WO2021238823A1 - 多链路试关联方法及相关装置 - Google Patents

多链路试关联方法及相关装置 Download PDF

Info

Publication number
WO2021238823A1
WO2021238823A1 PCT/CN2021/095343 CN2021095343W WO2021238823A1 WO 2021238823 A1 WO2021238823 A1 WO 2021238823A1 CN 2021095343 W CN2021095343 W CN 2021095343W WO 2021238823 A1 WO2021238823 A1 WO 2021238823A1
Authority
WO
WIPO (PCT)
Prior art keywords
mld
link
association
target
tentative
Prior art date
Application number
PCT/CN2021/095343
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 华为技术有限公司
Priority to EP21812460.0A priority Critical patent/EP4145947A4/en
Publication of WO2021238823A1 publication Critical patent/WO2021238823A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/086—Load balancing or load distribution among access entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H04W36/28—Reselection being triggered by specific parameters by agreed or negotiated communication parameters involving a plurality of connections, e.g. multi-call or multi-bearer connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • 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
    • 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
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a multi-link trial association method and related devices.
  • Wireless local area network (WLAN) roaming or Wi-Fi roaming refers to the transfer of a wireless terminal or station (station, STA) from one access point (access point, AP) to another AP, that is, the wireless terminal or the A process in which a STA moves from a basic service set (BSS) to another BSS.
  • STA wireless terminal or station
  • AP access point
  • BSS basic service set
  • STAs can move arbitrarily in Wi-Fi networks belonging to the same extended service set (ESS), such as switching from one BSS in the same ESS to another BSS; And through the user's identity (Internet Protocol (IP) address) does not change, that is, the IP address obtained by the client at the initial stage of connecting to the network does not change during the entire roaming process, so that the service is not interrupted (that is, the client's service is not interrupted ).
  • ESS extended service set
  • IP Internet Protocol
  • an STA When an STA roams from one AP to another AP, it will first disconnect from the original AP. Before the connection with the new AP is established, the AP and the STA cannot transmit service data. Therefore, in order to reduce the interruption time of data transmission during the roaming process, that is, to reduce the roaming delay (roaming delay refers to the time from when the STA disconnects from the original AP to the time it can transmit data with the new AP), it can be paired This is achieved by caching the pairwise master key (PMK).
  • PMK pairwise master key
  • the STA and the original AP complete the STA and the original AP (AP1 in Figure 1) through user association, 802.1X authentication process, unicast and multicast key negotiation, and encrypted data message communication.
  • the entire association negotiation of the original AP During the unicast and multicast key negotiation between the STA and the original AP, the STA will cache the PMK and/or PMK identification (ie PMKID), and the AP controller (AC) will also cache the PMK and/ Or PMKID.
  • PMKID PMK and/or PMK identification
  • AC AP controller
  • the STA initiates a re-association to the new AP (AP2 in Figure 1).
  • the re-association carries the PMKID buffered by the STA; after the new AP receives the PMKID, it sends the PMKID to the AC; the AC sends it through the new AP
  • the PMKID looks up whether the same PMKID information is stored locally. If so, it means that the STA has passed 802.1X authentication before and does not need to perform 802.1X authentication again, and directly derives the unicast multicast key with the new AP. After the unicast multicast key negotiation is completed, the STA can use the negotiated key to encrypt data and communicate with the new AP.
  • the STA fast roaming mechanism using PMK cache caches the PMKID, so that the STA directly skips the cumbersome 802.1X authentication process after switching the AP, thereby reducing the roaming delay.
  • the STA fast roaming mechanism that uses the PMK cache can only reduce the interruption time of data transmission during the roaming process, and cannot achieve uninterrupted data transmission.
  • the uninterrupted data transmission means that during the roaming process (or the process of switching from one BSS to another BSS, or the process of switching from one AP to another AP), there is always at least one link for data transmission.
  • Wi-Fi 7 also known as the extremely high throughput (EHT) standard
  • Wi-Fi 7 also known as the extremely high throughput (EHT) standard
  • EHT 7 extremely high throughput
  • multi-link multi-link
  • MLD multi-link devices
  • Multi-link devices mean that there are multiple RF modules at the same time, and the multiple RF modules work separately Devices on different frequency bands or channels. Therefore, for the roaming of multi-link devices, it is expected that the data transmission will not be interrupted.
  • how to achieve roaming of multi-link devices under IEEE 802.11be reduce the interruption time of data transmission during the roaming process, or make the data transmission during the roaming process uninterrupted, has not yet been resolved.
  • the embodiment of the application provides a multi-link trial association method and related devices, which can reduce the interruption time of data transmission during the roaming process when the multi-link device under IEEE 802.11be is roaming, and can control the update site and the connection
  • the timing of the in-point mapping information makes the data transmission uninterrupted during the roaming process.
  • the embodiments of the present application provide a multi-link trial association method, which is applied to a non-access point multi-link device (Non-AP MLD).
  • the Non-AP MLD includes multiple STAs
  • the multi-link Trial association methods include: one or more first STAs whose link status with the first AP MLD in Non-AP MLD is disconnected, generate and send multi-link associations to one or more second AP MLDs Request frame, the multi-link association request frame is used to initiate multi-link tentative association between Non-AP MLD and one or more second AP MLD;
  • Non-AP MLD receives one or more second AP MLD return If the one or more multi-link association response frames indicate that the multi-link tentative association is successful, the Non-AP MLD sends indication information to the target AP MLD to trigger the target
  • the AP MLD updates the mapping relationship between the site and the access point, and the target AP MLD is a second AP MLD determined from one or more second AP MLDs.
  • the link state between the second STA of the Non-AP MLD and the first AP MLD is the connected state.
  • the method for Non-AP MLD to determine the target AP MLD from one or more second AP MLDs is: Non-AP MLD according to whether the association between the Non-AP MLD and multiple second AP MLDs is successful, The capabilities of each second AP MLD and the link quality between the Non-AP MLD and each second AP MLD select a final target AP MLD from the multiple second AP MLDs.
  • This solution uses one or more STAs in the Non-AP MLD whose link state with the first AP MLD is disconnected, and initiates a multi-link tentative association with one or more second AP MLD at the same time. After success, send an indication message to inform the second AP that the MLD can update the mapping relationship between the station and the access point, so that the data packet from the Non-AP MLD can be correctly delivered to the corresponding AP MLD, realizing the IEEE 802.11be multi-chain
  • the interruption time of data transmission during the roaming process is reduced, and the data transmission during the roaming process can be uninterrupted by controlling the timing of updating the mapping information between the site and the access point.
  • the method further includes: the Non-AP MLD can send the MLD to the first AP MLD Send link state indication information, where the link state indication information is used to indicate that the link state between the first STA of the Non-AP MLD and the first AP MLD is in the disconnected state.
  • the link state indication information is also used to indicate the reason why the link state between the first STA of the Non-AP MLD and the first AP MLD is in the disconnected state.
  • the reason why the link state between the first STA and the first AP MLD is in the disconnected state is tentative association.
  • This solution uses link status indication information to inform the first AP that a certain or several links of the MLD are disconnected due to tentative association, avoiding the first AP MLD from trying to request the certain or certain link because of the large amount of data to be transmitted. Which certain links are open.
  • the embodiments of this application provide a multi-link trial association method, which is applied to a target AP MLD.
  • the target AP MLD includes multiple APs.
  • the multi-link trial association method includes: the target AP MLD receives from Non- The multi-link association request frame of the AP MLD, the multi-link association request frame is used to request the non-AP MLD to perform multi-link tentative association with the target AP MLD; if the target AP MLD returns the multi-link association response frame indicating the association If successful, the target AP MLD receives indication information from the Non-AP MLD.
  • the indication information is used to trigger the target AP MLD to update the mapping relationship between the station and the access point; after the target AP MLD receives the indication information, it sends the station to the access point.
  • the mapping information of the station and the access point is used to indicate that the mapping relationship between the station and the access point is updated from the association between Non-AP MLD and the first AP MLD to the association between Non-AP MLD and the target AP MLD.
  • the mapping information between the station and the access point includes the non-AP MLD service access point SAP media access control MAC address and the second AP MLD SAP MAC address.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a Non-AP MLD or a chip in Non-AP MLD, such as a Wi-Fi chip, including:
  • the processing unit is used to generate a multi-link association request frame; the transceiver unit is used to send a multi-link association request frame to one or more second APs MLD, and the multi-link association request frame is used to initiate Non-AP MLD and Multi-link tentative association between one or more second APs MLD; the transceiver unit is also used when the non-AP MLD is successfully associated with one or more second APs MLD’s multi-link tentative association , Sending indication information to the target AP MLD for triggering the target AP MLD to update the mapping relationship between the site and the access point, and the target AP MLD is a second AP MLD determined from one or more second AP MLDs.
  • the link state between the first STA and the first AP MLD is a disconnected state
  • the link state between the second STA of the Non-AP MLD and the first AP MLD is a connected state.
  • the above transceiver unit is also used to send link state indication information to the first AP MLD, where the link state indication information is used to indicate one or more of the non-AP MLD
  • the link state between the first STA and the first AP MLD is in the disconnected state.
  • the link state indication information is also used to indicate the reason why the link state between the first STA and the first AP MLD is in the disconnected state.
  • the reason why the link state between the first STA and the first AP MLD is in the disconnected state is tentative association.
  • an embodiment of the present application provides another communication device.
  • the communication device may be a target AP MLD or a chip in the target AP MLD, such as a Wi-Fi chip, including:
  • the transceiver unit is used to receive a multi-link association request frame from the Non-AP MLD, and the multi-link association request frame is used to request the Non-AP MLD to perform multi-link tentative association with the target AP MLD; the transceiver unit also When the multi-link association response frame returned by the target AP MLD indicates that the association is successful, receiving indication information from the Non-AP MLD, the indication information is used to trigger the target AP MLD to update the mapping relationship between the station and the access point; the processing unit, It is used to generate the mapping information between the station and the access point; the transceiver unit is also used to send the mapping information between the station and the access point, and the mapping information between the station and the access point is used to indicate the mapping relationship between the station and the access point.
  • the association between Non-AP MLD and the first AP MLD is updated to Non-AP MLD and the target AP MLD association.
  • the mapping information between the station and the access point includes the non-AP MLD service access point SAP media access control MAC address and the target AP MLD SAP MAC address.
  • the foregoing indication information may be carried in the A-control field or in a notification frame, such as a STA-AP Mapping Notify frame.
  • the foregoing multi-link association request frame may include the link state of the non-transmission link between the Non-AP MLD and the second AP MLD.
  • the multilink association request frame may also include a reason code field, and the reason code field may be used to indicate that the link state between the second STA of the Non-AP MLD and the second AP MLD is disconnected. s reason. Among them, the reason code field can be set to "associate with old AP MLD".
  • the link status of the non-transmission link between the Non-AP MLD and the second AP MLD is carried in the multi-link association request frame, which can avoid the second AP MLD because it does not know the Non-AP MLD and the second AP
  • the link state between MLDs, and the link whose link state is disconnected is used to transmit data to the Non-AP MLD.
  • the multi-link association request frame may further include tentative association indication information, which is used to indicate whether the current association operation is a multi-link tentative association.
  • the foregoing multi-link association request frame may further include tentative association life cycle information, which is used to indicate the life cycle of the multi-link tentative association.
  • the tentative association indication information and the tentative association lifetime information are carried in the common information field of the multi-link aggregation MLA element.
  • This solution carries tentative association indication information in the multi-link association request frame to distinguish between normal multi-link association and multi-link tentative association; by carrying tentative association lifetime information, Non-AP MLD can be compared with When there is no interaction between APs and MLDs for more than this life cycle, AP MLDs delete the information previously negotiated with Non-AP MLDs, thereby freeing up buffer space.
  • the embodiments of the present application provide a communication device, specifically Non-AP MLD, including a processor and a transceiver, and the processor is configured to support the Non-AP MLD to execute the corresponding method in the first aspect. Function.
  • the transceiver is used to support the communication between the Non-AP MLD and the AP MLD, and send the information, frames, data packets or instructions involved in the above methods to the AP MLD.
  • the Non-AP MLD may also include a memory, which is used for coupling with the processor and stores program instructions and data necessary for the Non-AP MLD.
  • the processor is used to generate a multi-link association request frame; the transceiver is used to send a multi-link association request frame to one or more second APs MLD, and the multi-link association request frame is used to initiate a non-AP MLD Multi-link tentative association with one or more second AP MLDs; this transceiver is also used when the non-AP MLD is successfully associated with one or more second AP MLD multi-link tentative associations
  • send indication information to the target AP MLD to trigger the target AP MLD to update the mapping relationship between the site and the access point.
  • the target AP MLD is a second AP MLD determined from one or more second AP MLDs.
  • an embodiment of the present application provides a communication device, specifically a target AP MLD, including a processor and a transceiver, and the processor is configured to support the target AP MLD to perform corresponding functions in the method of the second aspect.
  • the transceiver is used to support the communication between the target AP MLD and the Non-AP MLD, and send the information, frames, data packets or instructions involved in the above method to the Non-AP MLD.
  • the AP MLD may also include a memory, which is used for coupling with the processor and stores program instructions and data necessary for the AP MLD.
  • the transceiver is used to receive a multi-link association request frame from a Non-AP MLD, and the multi-link association request frame is used to request the Non-AP MLD to perform multi-link tentative association with the target AP MLD; the transceiver It is also used to receive indication information from the Non-AP MLD when the multi-link association response frame returned by the target AP MLD indicates that the association is successful, and the indication information is used to trigger the target AP MLD to update the mapping relationship between the site and the access point;
  • the processor is used to generate the mapping information between the station and the access point; the transceiver is also used to send the mapping information between the station and the access point, and the mapping information between the station and the access point is used to indicate the mapping relationship between the station and the access point Update from Non-AP MLD and first AP MLD association to Non-AP MLD and target AP MLD association.
  • an embodiment of the present application provides a wireless communication system, which includes the Non-AP MLD described in the third aspect or the fifth aspect, and the target in the fourth aspect or the sixth aspect.
  • AP MLD the Non-AP MLD described in the third aspect or the fifth aspect
  • AP MLD the target in the fourth aspect or the sixth aspect.
  • an embodiment of the present application provides a chip or chip system, including an input and output interface and a processing circuit, the processing circuit is used to generate a multi-link association request frame; the input and output interface is used to send one or more second The AP MLD sends a multi-link association request frame, which is used to initiate a multi-link tentative association between the Non-AP MLD and one or more second AP MLDs; the input/output interface is also used In the case of successful multi-link exploratory association between the Non-AP MLD and one or more second AP MLDs, send indication information to the target AP MLD to trigger the target AP MLD to update the mapping relationship between the station and the access point ,
  • the target AP MLD is a second AP MLD determined from one or more second AP MLDs.
  • the input and output interface is used to receive the multi-link association request frame from the Non-AP MLD, and the multi-link association request frame is used to request the non-AP MLD to perform multi-link with the target AP MLD.
  • Tentative association this input and output interface is also used to receive indication information from the Non-AP MLD when the multi-link association response frame returned by the target AP MLD indicates that the association is successful.
  • the indication information is used to trigger the target AP MLD update site and The mapping relationship of the access point; the processing circuit is used to generate the mapping information between the station and the access point; the input and output interface is also used to send the mapping information between the station and the access point, and the mapping information between the station and the access point is used
  • the mapping relationship between the indicated station and the access point is updated from the association between the Non-AP MLD and the first AP MLD to the association between the Non-AP MLD and the target AP MLD.
  • the present application provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the computer executes the multi-link test described in any of the above aspects. Association method.
  • the present application provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the multi-link trial association method described in any of the above-mentioned aspects.
  • the implementation of the embodiments of this application can reduce the interruption time of data transmission during the roaming process when the multi-link device under IEEE 802.11be is roaming, and can control the timing of updating the mapping information between the station and the access point to make the roaming process The data transmission is not interrupted.
  • Figure 1 is a schematic diagram of STA fast roaming using PMK cache
  • FIG. 2 is a schematic diagram of an architecture of a wireless communication system provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a multi-link device provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of the connection between AP multi-link equipment and Non-AP multi-link equipment
  • FIG. 5 is a schematic flowchart of a multi-link trial association method provided by an embodiment of the present application.
  • Fig. 6a is a schematic diagram of a frame structure of a new element provided by an embodiment of the present application.
  • FIG. 6b is a schematic diagram of a frame structure of another new element provided by an embodiment of the present application.
  • FIG. 7a is a schematic diagram of a frame structure of a neighbor report element provided in an embodiment of the present application.
  • FIG. 7b is a schematic diagram of a frame structure of a simplified neighbor report element provided by an embodiment of the present application.
  • FIG. 7c is a schematic diagram of a frame structure of a 12-byte TBTT information length field provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of interaction between Non-APMLD and an APMLD provided by an embodiment of the present application for performing 802.1X authentication and four-way handshake to derive PTK and GTK;
  • Figure 9a is a schematic diagram of part or all of the frame structure of a BSS transfer management query frame provided by an embodiment of the present application.
  • Figure 9b is a schematic diagram of part or all of the frame structure of a BSS transfer management request frame provided by an embodiment of the present application.
  • Figure 9c is a schematic diagram of part or all of the frame structure of a BSS transfer management response frame provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of Non-AP MLD switching AP MLD during roaming according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of the signaling interaction of Non-AP MLD switching AP MLD during roaming according to an embodiment of the present application
  • FIG. 12a is a schematic diagram of the conversion relationship between different states and the frame types allowed to be sent in different states according to an embodiment of the present application.
  • FIG. 12b is another schematic diagram of the conversion relationship between different states and the frame types allowed to be sent in different states according to an embodiment of the present application
  • Fig. 13a is a schematic diagram of interaction between Non-AP MLD and AP MLD in the initial association process provided by an embodiment of the present application;
  • FIG. 13b is another schematic diagram of interaction between Non-AP MLD and AP MLD in the initial association process provided by an embodiment of the present application;
  • FIG. 13c is another schematic diagram of interaction between Non-AP MLD and AP MLD in the initial association process provided by an embodiment of the present application;
  • FIG. 14 is a schematic diagram of an optimal association scenario in a Non-APMLD movement process provided by an embodiment of the present application.
  • 15 is a schematic flowchart of a method for associating non-co-located multi-link devices according to an embodiment of the present application
  • FIG. 16 is a schematic diagram of interaction between Non-AP MLD and AP MLD provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of another structure of a communication device provided by an embodiment of the present application.
  • the embodiment of the application provides a multi-link trial association method applied to a wireless communication system, which can reduce the interruption time of data transmission during the roaming process when a multi-link device under IEEE802.11be is roaming, and can be updated through control
  • the timing of the mapping information between the station and the access point makes the data transmission uninterrupted during the roaming process.
  • the wireless communication system may be a wireless local area network
  • the multi-link trial association method may be implemented by a communication device in the wireless communication system or a chip or processor in the communication device, and the communication device may be a type that supports parallel transmission of multiple links.
  • the communication device may be called a multi-link device or a multi-band device (multi-band device).
  • radio radio frequencies
  • Multi-radio (Radio) multi-link equipment includes multiple affiliated STAs.
  • the affiliated station may be an access point (access point, AP) or a non-access point station (non-access point station, non-AP STA).
  • this application refers to a multi-link device whose site is an AP may be called a multi-link AP or a multi-link AP device or an AP multi-link device (AP multi-link device, AP MLD), and the subordinate site
  • a multi-link device that is a non-AP STA may be called a multi-link Non-AP or a multi-link Non-AP device or a Non-AP multi-link device (Non-AP multi-link device, Non-AP MLD).
  • the multi-link device includes a subordinate station is also briefly described as "the multi-link device includes a station” in the embodiment of the present application.
  • the link identifier mentioned below is used to characterize the basic service set established by AP MLD on a certain channel in a certain frequency band, namely (Operating Class), channel number (channel number), and basic service set identifier (BSSID) ).
  • Non-AP MLD realizes through a certain subordinate STA through one association operation, Non-AP multiple subordinate STAs of MLD simultaneously associate with different APs of AP and MLD to establish multiple transmission links.
  • Non-AP MLD and AP MLD can indicate the corresponding link and the AP and Non-AP STA corresponding to both ends of the link through the link identifier. Therefore, when performing related signaling instructions between Non-AP MLD and AP MLD, only the corresponding link identifier needs to be carried, which reduces signaling overhead.
  • a management frame such as a beacon frame, sent by an AP multi-link device may carry elements including multiple link identification information fields.
  • Each link identification information field includes a link identification, and also includes one or more of BSS identifier, operation category, and channel number, where one or more of the BSS identifier, operation set, and channel number is associated with the link The logo corresponds.
  • AP MLD and Non-AP MLD negotiate multiple link identification information fields. In subsequent communications, AP MLD or Non-AP MLD will use link identifiers to characterize the stations at both ends of the corresponding link.
  • Multi-link devices can follow the IEEE 802.11 series of protocols to achieve wireless communication, for example, a site that follows a very high throughput rate, or a site based on IEEE 802.11be or compatible with IEEE 802.11be to achieve communication with other devices.
  • the multi-link trial association method provided in the embodiments of the present application can be applied to a multi-link device roaming scenario of a wireless communication system, such as at least one Non-AP multi-link device roaming between at least two AP multi-link devices In the scenario, or in a scenario where at least one Non-AP multi-link device switches from one BSS in the same ESS to another BSS.
  • the wireless communication system includes: multiple AP multi-link devices (the AP multi-link device 100 and the AP multi-link device 200 in FIG. 2), and a Non-AP multi-link device 300 .
  • the AP multi-link device is a multi-link device that provides services for the Non-AP multi-link device, and the Non-AP multi-link device can communicate with the AP multi-link device through multiple links, thereby Achieve the effect of improving throughput.
  • the numbers of AP multi-link devices and Non-AP multi-link devices in FIG. 2 are only exemplary.
  • the multi-link device (such as any one of the AP multi-link device 100, the AP multi-link device 200, and the Non-AP multi-link device 300 as shown in FIG. 2) is a wireless communication function A device, the device may be a complete device, or a chip or processing system installed in the complete device. The device installed with these chips or processing systems can implement this application under the control of these chips or processing systems.
  • the method and function of the embodiment for example, the Non-AP multi-link device in the embodiment of the present application has a wireless transceiver function, can support 802.11 series protocols, and can communicate with AP multi-link devices or other Non-AP multi-link devices.
  • Non-AP multi-link device is any user communication device that allows a user to communicate with an AP and then with a WLAN.
  • Non-AP multi-link devices can be tablet computers, desktops, laptops, notebook computers, ultra-mobile personal computers (UMPC), handheld computers, netbooks, and personal digital assistants (personal digital assistants). , PDA), mobile phones and other user equipment that can be connected to the Internet, or Internet of Things nodes in the Internet of Things, or in-vehicle communication devices in the Internet of Vehicles, etc.;
  • Non-AP multi-link devices can also be the chips and processing systems in these terminals .
  • the AP multi-link device in the embodiment of the present application provides a service for the Non-AP multi-link device and can support the 802.11 series of protocols.
  • AP multi-link devices can be communication entities such as communication servers, routers, switches, bridges, or AP multi-link devices can include various forms of macro base stations, micro base stations, relay stations, etc.
  • AP multi-link devices It may also be the chips and processing systems in these various forms of equipment, so as to realize the methods and functions of the embodiments of the present application.
  • multi-link devices can support high-rate and low-latency transmission.
  • multi-link devices can also be applied in more scenarios, such as sensor nodes in smart cities ( For example, smart water meters, smart meters, smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, televisions, stereos, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment Terminals (such as AR, VR and other wearable devices), smart devices in smart offices (such as printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, some infrastructure in daily life scenarios (such as vending machines, business Super self-service navigation desk, self-service cash register equipment, self-service ordering machine, etc.).
  • the 802.11 protocol may be a protocol that supports 802.11be or is compatible with 802.11be.
  • FIG. 3 is a schematic structural diagram of a multi-link device provided in an embodiment of the present application.
  • the IEEE 802.11 standard focuses on the 802.11 physical layer (PHY) and MAC layer in multi-link devices.
  • PHY physical layer
  • multiple STAs included in the multi-link device share a high MAC (high MAC) layer, but the low MAC (low MAC) layer and the PHY layer are independent of each other.
  • multiple STAs included in the multi-link device may also be independent of each other at the low MAC layer and PHY layer, and also independent of each other at the high MAC layer.
  • the embodiment of the present application does not limit the schematic diagram of the internal structure of the multi-link device, and FIG. 3 is only an exemplary illustration.
  • the high MAC layer or the low MAC layer may be implemented by one processor in the chip system of the multi-link device, and may also be implemented by different processing modules in one chip system.
  • the multi-link device may allow the same service identifier (traffic identifier, TID) service to be transmitted on different links at the same time, and even allow the same data packet to be transmitted on different links;
  • TID traffic identifier
  • the service of the same TID is allowed to be transmitted on different links, but the service of different TIDs is allowed to be transmitted on different links.
  • the frequency band in which the multi-link device works may include one or more frequency bands among sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz.
  • FIG. 4 is a schematic diagram of the connection between the AP multi-link device and the Non-AP multi-link device.
  • both the Non-AP multi-link device and the AP multi-link device adopt a structure shared by the high MAC layer.
  • the AP multi-link device includes two APs, and the Non-AP multi-link device includes two STAs.
  • An AP in the AP multi-link device can establish a link to communicate with a STA in the Non-AP multi-link device.
  • AP1 in the AP multi-link device in Figure 4 and the Non-AP multi-link device STA1 establishes link 1 for communication;
  • AP2 in the AP multi-link device in Figure 4 establishes link 2 with STA2 in the Non-AP multi-link device for communication.
  • the Non-AP multi-link device mentioned in the embodiment of this application may be the Non-AP multi-link device 300 in FIG. 2, and the first AP multi-link device may be the Non-AP multi-link device 300 in FIG. 2
  • the AP multi-link device 100, and the second multi-link device may be the AP multi-link device 200 in FIG. 2.
  • the Non-AP multi-link device in the embodiment of the present application may also be referred to as an STA multi-link device, so the Non-AP multi-link device and the STA multi-link device can be used interchangeably.
  • the multi-link devices in the embodiments of this application all support simultaneous transmit and receive (STR) on multiple links, or the multi-link devices in the embodiments of this application have STR capabilities.
  • a multi-link device with STR capability means that the channel spacing between any two radio frequency modules in the multi-link device is large enough so that any two radio frequency modules can not interfere with each other, can operate independently, and support in a chain While sending on the road, it can be received normally on the other link.
  • the embodiment of this application provides a multi-link trial association method, which uses multiple radio/links that can work simultaneously with Non-AP MLD, and tentatively associates with multiple APs MLD at the same time, so as to realize the multi-link device roaming Data transmission is not interrupted or the interruption time of data transmission is reduced.
  • FIG. 5 is a schematic flowchart of a multi-link trial association method provided by an embodiment of the present application.
  • the multi-link trial association method provided by the embodiment of the present application includes but is not limited to the following steps:
  • One or more second AP MLDs return a multi-link association response frame to the Non-AP MLD.
  • the non-AP MLD when there is only one Disable link between the Non-AP MLD and the first AP MLD, that is, when there is only one first STA in the Non-AP MLD, the non-AP MLD is the same as the first AP MLD.
  • the first STA whose link status is Disable sends a multi-link association request frame to a second AP MLD.
  • any first STA of the Non-AP MLD is The multi-link association request frame may be sent to a second AP MLD.
  • the multiple first STAs of the Non-AP MLD may send a multi-link association request frame to the multiple second APs MLD.
  • one or more second AP MLDs return a multi-link association response frame to the Non-AP MLD.
  • the multi-link association request (multi-link Association Request) frame may include the state of the non-transmission link between the Non-AP MLD and the second AP MLD, such as disable or enable.
  • the multilink association request frame may also carry a Reason Code field, which is used to indicate the reason why the link status between the Non-AP MLD and the second AP MLD is disabled. . Specifically, if the status of a certain link between the Non-AP MLD and the second AP MLD is disabled, the Reason Code field can be further used to indicate that the status of the link is disabled because the reason is energy saving and low signal reception.
  • the Reason Code field carried in the multi-link association request frame in the embodiment of the present application can be set to "associate with the old AP MLD".
  • a multi-link association operation can be performed on a certain link to achieve simultaneous establishment of associations with multiple links of the AP MLD.
  • the link that performs the multi-link association request/response frame interaction is called the transmission link (Transmitted Link), and the corresponding other links are called the non-transmitted link (Non-transmitted Link).
  • the multi-link association response frame may also indicate whether each AP in the second AP MLD is in the disable state or the enable state.
  • the state of the non-transmission link between the Non-AP MLD and the second AP MLD may also be implicitly indicated through TID-to-link mapping (TID-to-link mapping).
  • TID-to-link mapping can be carried in the multi-link association request/response frame, or after the interaction of the multi-link association request/response frame is completed, a separate TID-to-mapping request can be sent to indicate Non- The state of the non-transmission link between the AP MLD and the second AP MLD.
  • a multi-link association request (multi-link association request) frame may carry tentative association (Tentative Association) indication information, and optionally, it may also carry tentative association lifetime information.
  • the Tentative Association indication information can be used to indicate whether to perform a tentative association.
  • the field carrying the tentative association indication information is set to 1, indicating that the tentative association is performed; the field carrying the tentative association indication information is set to 0, indicating that the existing The normal association defined by the agreement. It is understandable that the embodiment of the present application does not limit the value and meaning of the field carrying the tentative association indication information.
  • Tentative Association lifetime information can be used to indicate the life cycle of the tentative association.
  • Tentative Association indication information and Tentative Association lifetime information may be carried in a common information field in a multi-link aggregation (multi-link aggregation, MLA) element of a multi-link association request frame.
  • Tentative Association indication information and Tentative Association lifetime information may also be carried in a newly defined element.
  • Fig. 6a is a schematic diagram of a frame structure of a new element provided in an embodiment of the present application. As shown in Figure 6a, the frame structure of this element includes the element identifier, length, control field, and tentative association lifetime. Among them, 1 bit is used in the control field to indicate whether to perform tentative association, and the remaining 7 bits are reserved.
  • the multi-link association request frame may carry a tentative association control field and a tentative association life cycle.
  • the tentative association control field includes three indication bits, namely the Non-AP MLD trigger 802.1X authentication indicator, the Non-AP MLD trigger four-way handshake indicator, and the Non-AP MLD trigger STA-AP mapping notification indicator.
  • Non-AP MLD when Non-AP MLD triggers the 802.1X authentication indicator position 1, it means that Non-AP MLD will actively send a message to trigger the start of the 802.1X authentication process; when the Non-AP MLD triggers the four-way handshake indicator position 1, it means Non-AP MLD will actively send a message to trigger the four-way handshake process; when Non-AP MLD triggers the STA-AP mapping notification indicator position 1, it means that Non-AP MLD will actively send a message to trigger the STA-AP mapping notification . It is understandable that the values and meanings of the three indicator bits included in the aforementioned tentative association control field are not limited.
  • the tentative association life cycle information can be used to indicate the life cycle of the tentative association. When there is no interaction between Non-AP MLD and AP MLD for more than this life cycle, AP MLD deletes the information previously negotiated with the Non-AP MLD .
  • the tentative association control field and the tentative association life cycle can be carried in a newly defined element.
  • Fig. 6b is a schematic diagram of a frame structure of another new element provided by an embodiment of the present application.
  • the frame structure of this element includes the element identifier, length, tentative association control field, and tentative association lifetime.
  • the tentative association control field includes 1-bit Non-AP MLD trigger 802.1X authentication indicator, 1-bit Non-AP MLD trigger four-way handshake indicator, and 1-bit Non-AP MLD trigger STA-AP mapping Notification indicator bit, the remaining 4 bits are reserved.
  • the Non-AP MLD may receive tentative association capability indication information sent by each AP MLD.
  • the capability indication information of the tentative association may be used to indicate whether the AP MLD supports tentative association.
  • the capability indication information of the tentative association may be carried in a fast BSS transition element, a multi-link aggregation (MLA) element, or a mobility domain element (Mobility Domain element).
  • the fast BSS transfer element may be carried in a beacon (Beacon) frame.
  • 1 bit can be added to the neighbor report element (neighbor report element) and the reduced neighbor report element (reduced neighbor report element) to indicate whether the neighbor AP or the neighbor AP MLD supports tentative association.
  • the neighbor report element can describe a neighbor AP and the BSS information on the neighbor AP.
  • the AP can indicate the related information of all neighbors by carrying multiple neighbor report elements.
  • the reserved bit in the BSSID information field in the neighbor report element is used to indicate whether the BSS supports tentative association.
  • the reserved bits in the BSS Parameter field in the condensed neighbor report element are used to indicate whether the BSS supports tentative association.
  • FIG. 7a is a schematic diagram of a frame structure of a neighbor report element provided in an embodiment of the present application.
  • the neighbor report elements include element identifier, length, BSS identifier, BSSID information, operation type, channel number, physical layer type, and optional sub-elements.
  • the BSSID field is used to indicate the BSSID corresponding to the reported neighbor AP;
  • the BSSID information field is used to indicate the related information of the reported BSSID;
  • the Operating Class field and the channel Number field are used to indicate the reported BSSID On which channel;
  • the PHY Type (physical layer type) field is used to indicate the physical layer type of the AP corresponding to the reported BSSID;
  • the Optional subelements field carries some optional subelements.
  • the BSSID information field it carries the following specific information: 1. AP Reachability field: indicates whether the AP is reachable. 2. Security field: indicates whether the reported AP supports the same security configuration as the existing connection. 3. Key Scope field: Indicate whether the reporting AP and the reporting AP are the same authenticator. 4. Capabilities field: indicates some optional capability information of the reported AP. 5. Mobility domain field: indicates whether the reporting AP and the reporting AP are in the same mobility domain. 6. High Throughput field: indicates that the HT capabilities element of the reported AP (carried in the optional subelement field) is the same as the HT capabilities element of the AP that sent the report. 7.
  • Very High Throughput field indicates that the VHT capabilities element of the reported AP is the same as the VHT capabilities element of the AP that sent the report.
  • FTM fine timing measurement
  • High Efficiency field indicates that the HE capabilities element of the reported AP is the same as the HE capabilities element of the AP that sent the report.
  • ER Extended range
  • BSS indicates that the Beacon sent by the reported AP is sent in HE ER SU PPDU mode.
  • Collocated AP field indicates whether the reporting AP and the reporting AP are co-located APs.
  • Unsolicited Probe Response Active field Indicate whether the reported AP enables active probe response. 13.
  • Member of ESS with 2.4/5GHz co-located AP field indicates whether the reported AP is co-located with a 2.4/5GHz AP and is a member of an extended service set. 14.
  • OCT supported with reporting AP field indicates whether the reporting AP supports the OCT (On-channel tunneling) mechanism to exchange management frame type MPDUs.
  • Co-located with 6GHz AP field indicates whether the reported AP is co-located with a 6GHz AP. 16. Reserved fields.
  • Capabilities field it also specifically has the following information fields: Spectrum management field: indicates whether the reported AP supports the spectrum management function; QoS (quality of service) field: indicates whether the reported AP supports the QoS mechanism; APSD( The automatic power save delivery field: indicates whether the reported AP supports the automatic energy-saving transmission mechanism; the Radio Measurement field: indicates whether the reported AP supports the wireless measurement function.
  • AP MLD can carry a simplified neighbor report element in management frames, such as beacon frames, and probe response frames.
  • Non-AP MLD scans, it receives the association frame sent by AP MLD, so as to obtain neighboring AP information, and then select the appropriate AP MLD for association.
  • FIG. 7b is a schematic diagram of a frame structure of a simplified neighbor report element provided in an embodiment of the present application.
  • the simplified neighbor report element includes an element identifier, a length, and one or more neighbor AP information fields.
  • a neighbor AP information field includes a target beacon transmission time (TBTT) information field header, operation type, channel number, and TBTT information set.
  • the TBTT information set includes one or more TBTT information fields.
  • the TBTT info Field Type field is used to indicate the type of TBTT info, which together with the TBTT information length field indicates the format of the TBTT info field;
  • the Filtered neighbor AP field is used to indicate this Whether the SSIDs of all BSSs carried in the Neighbor AP info field match the SSID in the Probe Request frame; Reserved field (1 bit);
  • TBTT info count field used to indicate the number of TBTT information fields in the TBTT information set;
  • TBTT info The Length field is used to indicate the length of each TBTT info field.
  • FIG. 7c is a schematic diagram of a frame structure of a 12-byte TBTT information length field provided in an embodiment of the present application.
  • the 12-byte TBTT information length field includes the neighbor AP's TBTT offset, BSS identifier, short service set identifier, and BSS parameters.
  • Neighbor AP TBTT offset field indicates the offset of the Beacon transmission time between the reported BSS and the BSS that sent the Report.
  • BSSID field indicates the BSS identifier corresponding to the reported BSS.
  • Short SSID field indicates the service set identifier to which this BSS belongs.
  • BSS Parameter (BSS parameter) field indicates related parameters of the BSS.
  • the BSS Parameter field specifically contains the following indication information: (1) OCT recommended (recommended use of channel-based tunneling mechanism) field: indicates that the reported BSS expects to exchange management type MPDUs with it through the OCT mechanism. (2) Same SSID (Same Service Set Identifier) field: indicates whether the reporting AP and the reporting AP have the same SSID. (3) Multiple BSSID (Multiple Basic Service Set Identifier) field: indicates whether the reported AP is part of a multiple BSSID set. (4) Transmitted BSSID (Transmitted Basic Service Set Identifier) field: If the reported AP is part of a multiple BSSID set, it further indicates whether the reported AP is a Transmitted BSSID or a non-transmitted BSSID.
  • OCT recommended (recommended use of channel-based tunneling mechanism) field indicates that the reported BSS expects to exchange management type MPDUs with it through the OCT mechanism.
  • Same SSID Shorte Service Set Identifier
  • Multiple BSSID Multiple Basic Service Set Identifier
  • Co-located AP indicates whether the reported AP is co-located with a 2.4/5GHz AP (that is, whether it is 6GHz or not). only AP) and is a member of an extended service set.
  • Unsolicited Probe Response Active (active probe response) field indicates whether the reported AP enables active probe response.
  • the Non-AP MLD performs 802.1X authentication with one or more second AP MLDs and the four-way handshake derives PTK and GTK processes.
  • FIG. 8 is a schematic diagram of the interaction between a Non-AP MLD and an AP MLD for 802.1X authentication and four-way handshake to derive PTK and GTK according to an embodiment of the present application.
  • AP MLD sends an Extensible Authentication Protocol (EAP) request/identity to Non-AP MLD; Non-AP MLD returns EAP response/identity to AP MLD; AP The MLD sends a Radius access request to an authentication server (AS), and a series of interactions. After the EAP succeeds, a four-way handshake process is performed to derive the PTK and GTK.
  • EAP Extensible Authentication Protocol
  • AS authentication server
  • the process of deriving PTK and GTK from the four-step handshake includes: Non-AP MLD sends key message 1 (Key Message1) to AP MLD; AP MLD returns key message 2 (Key Message2) to Non-AP MLD; Non-AP MLD sends Key Message 3 (Key Message 3) to AP MLD; AP MLD returns Key Message 4 (Key Message 4) to Non-AP MLD.
  • Non-AP MLD and AP MLD use the corresponding secret key for encryption according to the type of data message sent.
  • Non-AP MLD performs 802.1X authentication with multiple second APs MLD and the four-way handshake derives PTK and GTK process
  • Non-AP MLD can simultaneously perform 802.1X authentication and four-way handshake derivation of PTK and GTK processes with multiple second AP MLDs, so as to improve the success rate of roaming.
  • a first STA in Non-AP MLD can perform 802.1X authentication with a second AP MLD and the four-way handshake derives PTK and GTK processes, so multiple first STAs in Non-AP MLD can communicate with multiple The second AP MLD performs 802.1X authentication and four-way handshake to derive the PTK and GTK process.
  • Non-AP MLD determines the final target AP MLD from one or more second AP MLDs.
  • the Non-AP MLD sends an indication message to the target AP MLD for triggering the target AP MLD to update the mapping relationship between the station and the access point in the distribution system (distribution system, DS).
  • the above-mentioned indication information may be carried in the A-Control (A-Control) field.
  • the indication information may also be carried in a newly defined frame.
  • the frame carrying the indication information is referred to as a STA-AP Mapping Notify frame in the following. It is understandable that the frame carrying the indication information may also be referred to as a STA-AP Mapping trigger frame, etc.
  • the embodiment of the present application does not limit the name of the frame carrying the indication information.
  • the Non-AP MLD may be based on whether the Non-AP MLD is successfully associated with multiple second APs MLDs, the capabilities of each second AP MLD, and the link between the Non-AP MLD and each second AP MLD Road quality, select a final target AP MLD from the multiple second AP MLDs. It is understandable that when there is only one second AP MLD, the Non-AP MLD directly sends the indication information to the second AP MLD.
  • Non-AP MLD uses a certain or certain Disable links and one or more second AP MLDs to perform Multi-link Tentative Association ( Multi-link tentative association), perform various operations/processes, except for triggering the sending of the DS-STA-Notify.request primitive.
  • Multi-link tentative association Multi-link tentative association
  • Non-AP MLD can set the status of the two links with the first AP MLD to disable, and then use the corresponding STA to communicate with the neighboring STA at the same time.
  • Two second AP MLDs perform Tentative Reassociation.
  • Non-AP MLD decides which second AP MLD to re-associate with based on whether the association is successful, the capabilities of the two adjacent second AP MLDs, and the link quality between the Non-AP MLD and each second AP MLD, and then Non- AP MLD can skip 802.1X authentication and directly derive PTK and/or GTK.
  • Non-AP MLD can skip 802.1X authentication, Non-AP MLD needs to send a newly defined frame to trigger the four-way handshake with the new AP MLD to derive PTK and GTK.
  • the process of the multi-link trial association method provided by the embodiment of the present application may be more than that of the foregoing step 101 to step S104.
  • the following will describe the processes that may also be included in the multi-link trial association method provided in the embodiment of the present application.
  • step S106 is further included:
  • Non-AP MLD sends link state indication information to the first AP MLD, and the link state indication information is used to indicate the relationship between the Non-AP MLD and the first AP MLD The link status of the link is Disable.
  • the link state indication information may include one or more link identifiers between the Non-AP MLD and the first AP MLD and the state corresponding to each link identifier.
  • the link status indication information may also indicate the reason why the status of one or more links between the Non-AP MLD and the first AP MLD is Disable.
  • the reason why the link state between the Non-AP MLD and the first AP MLD is Disable may include one of energy saving, low received signal strength indication, and tentative association. It is also understandable that the reason why the state of one or more links between the Non-AP MLD and the first AP MLD indicated by the link state indication information in the embodiment of the present application is Disable is tentative association.
  • the embodiment of this application informs the first AP MLD that a certain link or certain links are Disabled due to tentative association through link status indication information, avoiding the first AP MLD from trying to request the certain link because of the large amount of data to be transmitted Or the certain links are open.
  • Non-AP MLD sends a first request to the first AP MLD, and the first request is used to request the first AP MLD to feed back neighbor information of the first AP MLD .
  • the neighbor information here may refer to other APs MLD around the first AP MLD, or other BSSs around the BSS where the first AP MLD is located.
  • the Non-AP MLD may send a BSS Transition Management Query frame to the first AP MLD, and the BSS Transition Management Query frame is used to request the first AP MLD to feed back neighbor information around the first AP MLD .
  • the first AP MLD sends a BSS Transition Management Request (BSS Transition Management Request) frame to the Non-AP MLD.
  • BSS Transition Management Request BSS Transition Management Request
  • BSS Transition Management Response BSS Transition Management Response
  • the BSS transfer management inquiry frame may include a BSS transfer inquiry reason field and a BSS transfer candidate list field.
  • the BSS transfer inquiry reason field may be used to indicate the reason for the BSS transfer management inquiry;
  • the BSS transfer candidate list field may carry one or more neighbor report information elements (Neighbor Report elements).
  • Figure 9a is a schematic diagram of part or all of the frame structure of a BSS transfer management query frame provided by an embodiment of the present application.
  • the above BSS transfer management request frame may include the following fields: Perferred Candidate List included indicator bit (Bit 0), abridged indicator bit (Bit 1), immediate disassociation (Disassociation Imminent) indicator Bit (Bit 2), BSS Termination Included indicator bit (Bit 3), ESS Disassociation Imminent indicator bit (Bit 4), Disassociation Timer field, and Validity Interval ) Fields and so on.
  • FIG. 9b is a schematic diagram of a part or all of the frame structure of a BSS transfer management request frame provided by an embodiment of the present application.
  • Perferred Candidate list included indicates position 0, it means Non-AP MLD can ignore the information in the BSS Transfer Candidate List field; when Perferred Candidate list includes indicates position 1, it means AP MLD wants Non-AP MLD can process the information in the BSS Transition Candidate List field.
  • the Disassociation Imminent indicator bit is used to indicate whether the Non-AP MLD will be disassociated.
  • Disassociation Imminent When Disassociation Imminent indicates position 1, it means that the Non-AP MLD will be immediately disassociated by AP MLD; when Disassociation Imminent indicates position 0, it means that disassociation will not happen immediately.
  • the BSS Termination Included indicates the position is 1, it means that the BSS will be terminated; when the BSS Termination Included indicates the position is 0, it means that the BSS Termination Duration field will not be carried.
  • the ESS Disassociation Imminent indicator bit is used to indicate whether the session information universal resource locator (Session Information URL) field is carried and the Non-AP MLD will be disassociated by the ESS.
  • the Disassociation Timer field is used to indicate how long the AP MLD will send a disassociation frame to the Non-AP MLD.
  • the Validity Interval field is used to indicate the validity period of the BSS transition candidate list information.
  • the aforementioned BSS transfer management response frame may include a BSS transfer management status code (BTM Status Code) field, a BSS Termination Delay (BSS Termination Delay) field, a target BSS ID (Target BSSID), a BSS transfer candidate list field, and so on.
  • BTM Status Code BSS Transfer management status code
  • BSS Termination Delay BSS Termination Delay
  • target BSS ID target BSS ID
  • BSS transfer candidate list field a BSS transfer management response frame
  • FIG. 9c is a schematic diagram of part or all of the frame structure of a BSS transfer management response frame provided by an embodiment of the present application.
  • the BTM Status Code field is used to indicate the status information fed back to the BSS handover request, such as indicating whether to accept the BSS handover.
  • the BSS Termination Delay field is used to indicate how long the Non-AP MLD expects the AP MLD to terminate the BSS.
  • Target BSSID is used to indicate the identification of the target BSS for hand
  • the target BSS identifier in the BSS transfer management response frame in the embodiment of the present application may carry the service access point (service access point, SAP) MAC Address of the target AP MLD.
  • SAP service access point
  • step S107 may also be: the Non-AP MLD actively sends a BSS transfer management query frame to the first AP MLD, requesting the first AP MLD to provide its neighbor information.
  • step S107 may also be: Non-AP MLD jumps to other channels (here, other channels may refer to channels different from the channel of the first AP MLD) to perform active or passive scanning to obtain the first AP MLD neighbor information.
  • step S104 it further includes step S108: the target AP MLD sends the DS-STA-Notify.request primitive to the distributed system.
  • the DS-STA-Notify.request primitive carries the mapping information between the target AP MLD and the Non-AP MLD, or the association relationship between the target AP MLD and the Non-AP MLD.
  • the DS-STA-Notify.request primitive is used to inform the STA-AP Mapping information of the distributed system.
  • each Non-AP MLD can only be associated with one AP MLD, and the distributed system must know which AP MLD serves the Non-AP MLD, and then deliver the data packet whose destination address is the MAC address of the Non-AP MLD to the corresponding AP MLD.
  • the Non-AP MLD may negotiate a block acknowledgement (BA) with the target AP MLD.
  • BA block acknowledgement
  • the foregoing DS-STA-Notify.request primitive may carry the SAP MAC address of the Non-AP MLD and the update type (Update Type).
  • the update type can include three types: ADD (add), MOVE (move) and DELETE (delete).
  • ADD is used in the DS-STA-Notify.request primitive sent by AP MLD when Non-AP MLD associates with an AP MLD for the first time.
  • DELETE is used in the DS-STA-Notify.request primitive sent by the AP MLD when the Non-AP MLD is disassociated from an AP MLD for the first time.
  • MOVE is used in the DS-STA-Notify.request primitive sent by AP MLD when Non-AP MLD switches from a certain AP MLD to a new AP MLD.
  • the update type carried in the DS-STA-Notify.request primitive sent by the target AP MLD in this embodiment of the application is MOVE.
  • the MAC Address in the DS-STA-Notify.request primitive sent by the target AP MLD is the SAP MAC Address of the Non-AP MLD.
  • Non-AP MLD and SAP MAC Address of AP MLD are also used in the foregoing STA-AP Mapping information.
  • step S109 is further included: if the channel is idle for a period of time without data transmission between the first AP MLD and the Non-AP MLD for more than a predetermined time, the Non-AP MLD can take the initiative to transfer to the first AP MLD and the Non-AP MLD.
  • An AP MLD sends a multi-link disassociation frame. Then, Non-AP MLD can switch one or more second STAs whose status of the remaining link with the first AP MLD is enable to the channel of the link corresponding to the target AP MLD, and notify the target AP MLD of this one Or the link state between the multiple second STAs and the target AP MLD becomes the Enable state.
  • the Non-AP MLD immediately sends a multi-link disassociation frame to the first AP MLD, and switches to the channel of the link corresponding to the target AP MLD, and informs the target AP MLD of the link The status changes to the Enable status.
  • step S108 and the above step S109 can be performed at the same time, step S108 can also be performed before step S109, and step S108 can also be performed after step S109.
  • the embodiment of the present application sets out the order of execution between step S108 and step S109. Not limited.
  • the Non-AP MLD disconnects part of the link with the currently associated AP MLD (that is, the first AP MLD), and then uses the STA whose link status is disconnected to send to one or more second APs.
  • MLD sends a multi-link association request frame to request multi-link tentative association with the one or more second AP MLD; one or more second AP MLD returns a multi-link association response frame to the Non-AP MLD; if The multi-link association response frame indicates that the multi-link tentative association is agreed to, and the Non-AP MLD can perform 802.1X authentication and the four-way handshake key exchange process with one or more second AP MLDs; in the four-way handshake exchange After the secret key is completed, Non-AP MLD selects a target from one or more second AP MLD according to whether the association is successful, the capabilities of each second AP MLD, and the link quality between the Non-AP MLD and each second AP MLD AP MLD, and triggers the target AP MLD
  • Example 1 shows a specific process of the multi-link trial association method provided in the first embodiment
  • Example 2 shows a signaling interaction process of the multi-link trial association method provided in the first embodiment.
  • the first AP multi-link device is AP MLD1
  • the second AP multi-link device is AP MLD2
  • AP MLD1 includes AP11 and AP12
  • AP MLD2 includes AP21 and AP22
  • Non -AP multi-link equipment includes STA1 and STA2.
  • Non-AP multi-link devices are associated with AP MLD1 before roaming.
  • Example 1 Refer to FIG. 10, which is a schematic diagram of a Non-AP MLD switching AP MLD during a roaming process according to an embodiment of the present application.
  • STA2@Non-AP MLD means STA 2 of Non-AP MLD;
  • CH means channel;
  • CH1@Band 1 means channel 1 on band 1.
  • the process of non-AP MLD switching AP MLD during roaming includes but not limited to the following steps:
  • Step 1 Non-AP MLD sends link status indication information to AP MLD1.
  • the link status indication information is used to indicate that the status of the link 12 (link 12) is disconnected (or Disable).
  • the link status indication information may carry a link ID (link ID) corresponding to link 12, and the notification information may also indicate that the status of link 12 is Disable.
  • the link status indication information may also carry a reason code (Reason Code) field to indicate the reason why the status of the link 12 is Disable.
  • the reason that the link status is disconnected (or Disable) can be power save, or low received signal strength indication (Low RSSI), or tentative association (tentative association) and many more.
  • the Reason Code (Reason Code) field carried in the link state indication information in the embodiment of the present application can be set to a tentative association (tentative association).
  • the link state indication information may be sent through link 11 (link 11), or may be sent through link 12, which is not limited in the embodiment of the present application. It is understandable that no matter which link the link state indication information is sent through, the information it carries does not change.
  • Step 2 Non-AP MLD STA2 (i.e. STA2@Non-AP MLD) jumps to channel 2 (i.e. CH2@Band 4) of band 4, and initiates a multi-link exploratory association with AP MLD2.
  • STA2@Non-AP MLD i.e. STA2@Non-AP MLD
  • STA2@Non-AP MLD switches to link 22 (link 22) to start BSS transfer, first conducts the 802.11 open authentication process with AP MLD2, and then sends a multi-link reassociation request (multi-link reassociation request) Frame
  • the multi-link re-association request frame may carry tentative association indication information
  • the tentative re-association indication information may be used to indicate whether the type of this re-association operation is a tentative association, or to indicate the multi-link re-association Whether the type of association operation requested by the request frame is a tentative association.
  • the tentative association indication information may be carried in the common information (common information) field of the multi-link aggregation (MLA) element (MLA) of the multi-link re-association request frame.
  • the multi-link re-association request frame may also indicate that the status of the link 21 (link 21) is Disable. This is because STA 1 of Non-AP MLD (ie STA1@Non-AP MLD) and AP MLD1 have not been disconnected yet, that is, the state of link 11 between STA1 and AP11 is enable. Further optionally, the multi-link re-association request frame may also carry a Reason Code field to indicate the reason that the status of the link 21 is Disable. The Reason Code field here can be set to "Association with old AP MLD (Association with old AP MLD)".
  • Non-AP MLD can use a new SAPMAC Address of Non-AP MLD when reassociating with AP MLD2 or multi-link tentative reassociation.
  • the Non-AP MLD carries both the new SAP MAC Address and the old SAP MAC Address of the Non-AP MLD in the multi-link re-association request frame.
  • the old SAP MAC Address of Non-AP MLD can be used by AP MLD2 to retrieve uncompleted data packets from AP MLD1.
  • the old SAP MAC Address of Non-AP MLD may refer to the SAP MAC Address used when Non-AP MLD is associated with AP MLD1.
  • Non-AP MLD since the Non-AP MLD adopts the new SAP MAC Address and AP MLD2 to perform multi-link tentative re-association, the Non-AP MLD needs to perform 802.1X authentication again.
  • Step 3 The AP MLD2 returns a multi-link re-association response (lulti-link association response) frame to the STA 2 of the Non-AP MLD on the link 22.
  • the Non-AP MLD can perform negotiation and interaction operations such as BA Agreement establishment with the AP MLD 2, and the AP MLD 2 cannot send DS-STAs -Notify.request primitive to notify the distributed system to update the STA-AP Mapping information.
  • Step 4 Non-AP MLD sends a STA-AP Mapping Notify frame to AP MLD 2 at a certain moment to trigger AP MLD 2 to send DS-STA-Notify.request primitive to notify DS to update STA-AP Mapping information.
  • the STA-AP Mapping Notify frame when the Non-AP MLD sends the STA-AP Mapping Notify frame can be determined by combining various factors. For example, the STA-AP Mapping Notify frame is sent when the association between Non-AP MLD and AP MLD2 is better than the association between Non-AP MLD and AP MLD1.
  • Step 5 AP MLD2 returns an acknowledgement frame to Non-AP MLD, and sends DS-STA-Notify.request primitive to notify DS to update STA-AP Mapping information.
  • the DS-STA-Notify.request primitive carries the Non-AP MLD service access point (service access point, SAP) MAC address, and the update type carried by the DS-STA-Notify.request primitive is MOVE.
  • SAP service access point
  • the AP MLD2 sends the DS-STA-Notify.request primitive to notify the DS to update the STA-AP Mapping information, it can go to the AP MLD1 to obtain the incomplete data transmitted to the Non-AP MLD.
  • Step 6 STA1 of Non-AP MLD (ie STA1@Non-AP MLD) sends a multi-link disassociation frame to AP MLD1, and then jumps to channel 1 of band 3 (ie CH1@Band 3 ) To exchange data with AP 21 of AP MLD2 (ie AP 21@AP MLD 2).
  • the Non-AP MLD to notify the AP that the state of the MLD2 link 21 (link 21) becomes enable
  • implicit notification is: if Non-AP MLD has uplink data to be transmitted, Non-AP MLD can directly send uplink data on link 21 (link 21), and implicitly notify AP MLD2 through uplink data on link 21, The status of link 21 has changed to enable.
  • the explicit notification is: if the Non-AP MLD has no uplink data to transmit, the Non-AP MLD can send a QoS Null frame to the AP MLD2 to notify the AP MLD 2 that the status of the link 21 has become enable. Or the AP MLD2 is notified by carrying the link identifier and status information of link21 in the A-Control field of the data frame sent on link22.
  • STA1 of Non-AP MLD can set a time value. If the time of no data transmission between AP MLD1 and Non-AP MLD exceeds this time value in the channel idle state, STA1 of Non-AP MLD can actively send a multi-link disassociation frame to AP MLD1.
  • Non-AP MLD and AP MLD1 carry a time value when they are associated. If there is no data transmission time between AP MLD1 and Non-AP MLD in the channel idle state for more than this time value, Non-AP MLD can automatically disconnect the link without the Non-AP MLD sending a multi-link disassociation frame to AP MLD1.
  • the STA1 of the Non-AP MLD may send a multilink disassociation frame to the AP MLD1.
  • the process of switching between APs and MLDs of Non-AP MLD during roaming may be less than the steps shown in FIG. 10, or may be more than the steps shown in FIG. 10. This is not done in this embodiment of the application. limited.
  • Non-AP MLD disconnects one or part of the link with the currently associated AP MLD (ie AP MLD1); then uses the STA whose link status is disconnected to connect to the new target AP MLD (ie AP MLD2) Perform multi-link association; after the four-way handshake derives PTK and GTK, the target AP MLD (ie AP MLD2) sends the DS-STA-Notify.request primitive to notify the DS to update the STA-AP Mapping information, and to the previous
  • the associated AP MLD retrieves the uncompleted data transmitted to the Non-AP MLD.
  • the interruption time of data transmission can be reduced. Ideally, there is no interruption of data transmission, that is, at any time, there is always an available link for data transmission.
  • Example 2 Refer to FIG. 11, which is a schematic diagram of the signaling interaction of the Non-AP MLD switching AP MLD during the roaming process provided by the embodiment of the present application.
  • the process of Non-AP MLD switching AP during roaming MLD may not include step 4 in Figure 10, that is, STA2 of Non-AP MLD does not need to send STA-AP Mapping Notify frame to AP MLD 2 to trigger AP MLD 2 Send the DS-STA-Notify.request primitive.
  • This embodiment of the application restricts the AP MLD2 to directly send the DS-STA-Notify.request primitive to the DS after receiving the Key Message 4, so as to realize the DS to update the STA-AP Mapping information.
  • Non-AP MLD can immediately send a multi-link disassociation frame to AP MLD1 after receiving the ACK frame returned by AP MLD2 for Key Message 4, and then switch to the link channel corresponding to AP MLD2 and notify AP MLD2 The link state becomes the enable state.
  • Non-AP MLD can also receive the ACK frame returned by AP MLD2 for Key Message 4, and if the channel is idle for no data transmission time between AP MLD1 and Non-AP MLD exceeds a certain value, then Non-AP MLD actively sends a multi-link disassociation frame to AP MLD1, then switches to the link channel corresponding to AP MLD2, and notifies AP MLD2 that the link status becomes the enable state.
  • Embodiment 1 of this application introduces Tentative Association in the process of association/re-association of multi-link devices to achieve uninterrupted data transmission, the frame types allowed to be transmitted between Non-AP MLD and AP MLD in different states It also needs to be redefined.
  • FIG. 12a is a schematic diagram of the conversion relationship between different states and the frame types allowed to be sent in different states according to an embodiment of the present application.
  • State 5 is a newly added state in the embodiment of the present application.
  • the frames allowed to be transmitted include frame category 1, frame category 2, frame category 3, and frame category 4 data frames, control frames, or management frames.
  • various frames under frame category 1 and frame category 2 are the same as existing protocols.
  • the data frame in frame category 3 can refer to: in the basic BSS and the grid BSS, the data frame between the sites of the Ethernet type is not equal to 0X0800 or 0X86dd (Data frames between STAs with Ethernet_Type not equal to 0X0800 or 0X86dd in an infrastructure BSS or in an MBSS).
  • frame category 3 can mean that Address 3 in the MAC frame header is the BSSID of the currently associated AP; frame category 4 can mean that Address 3 in the MAC frame header is non-current The MAC address of the BSSID of the associated AP. It is understandable that before the AP MLD sends the DS-STA-Notify.request primitive, this embodiment of the application only allows transmission of various frames in frame types 1, 2, and 3. After AP MLD sends DS-STA-Notify.request primitive or Non-AP MLD sends STA-AP Mapping Notify frame, the embodiment of this application allows any frame to be transmitted, such as each of frame types 1, 2, 3, and 4. Kind of frame.
  • the Non-AP MLD is allowed to directly communicate with the DS, whereas before, only the AP MLD is allowed to communicate with the DS in a proxy manner.
  • FIG. 12b is another schematic diagram of the conversion relationship between different states and the frame types allowed to be sent in different states according to an embodiment of the present application. As shown in Figure 12b, no new states are added in this embodiment of the application. In state 4, data frames, control frames, or management frames in frame category 1, frame category 2, frame category 3, and frame category 4 are allowed to be transmitted.
  • the embodiment of the present application also provides an initial association method for multi-link devices.
  • the initial association method uses multiple Radios of Non-AP MLD to initiate tentative association with multiple APs MLD (or AP) at the same time, and then according to the association situation, Choosing the best AP MLD (or AP) for association can increase the non-AP MLD association success rate in the initial association process and increase the association speed.
  • the second embodiment of the present application can be separately applied to the initial association scenario of Non-AP MLD and AP MLD, or can be applied together in combination with the first embodiment, which is not limited in this embodiment of the present application.
  • FIG. 13a is a schematic diagram of interaction between Non-AP MLD and AP MLD in the initial association process provided in an embodiment of the present application.
  • three AP MLDs and one Non-AP MLD are taken as an example to describe the initial association method provided in the embodiment of the present application.
  • the initial association method includes: (1) Non-AP MLD initiates an association with an AP MLD (AP MLD1 in Figure 13a) on a link (Link 1 in Figure 13a), and instructs to associate with the AP The other links of MLD 1 are in the Disable state, followed by 802.1X authentication to obtain PMK; (2) Non-AP MLD uses the remaining multiple links (such as link 2 and link 3 in Figure 13a) on different channels Send a Multi-link Re-association Request frame to initiate a tentative association with multiple APs MLDs (AP MLD2 and AP MLD3 in Figure 13a), and indicate the other in the association request frame The link is in the Disable state; (3) Non-AP MLD is based on whether the association is successful, the capabilities of each AP MLD (AP MLD1, AP MLD2, AP MLD3 in Figure 13a), and the link quality between Non-AP MLD and each AP MLD , Determine the target AP MLD, that is, determine which AP MLD is ultimately associated with, and then derive
  • Non-AP MLD can send a newly defined frame to trigger a four-way handshake with the target AP MLD to derive PTK and GTK.
  • Non-AP MLD only needs to perform 802.1X authentication once, and does not need to perform multiple 802.1X authentications with multiple AP MLDs, which can reduce Non-AP MLD.
  • AP MLD's association delay during the initial association process improves the association speed.
  • FIG. 13b is another schematic diagram of interaction between Non-AP MLD and AP MLD in the initial association process provided by an embodiment of the present application.
  • three AP MLDs and one Non-AP MLD are taken as an example to illustrate the initial association method provided in the embodiment of the present application.
  • the initial association method includes: (a) Non-AP MLD sends a multi-link association request (Multi-link Association) on multiple links (such as link 1, link 2, and link 3 in Figure 13b) Request) frame, initiate a tentative association with multiple AP MLDs (AP MLD1, AP MLD2, and AP MLD3 in Figure 13b) at the same time, and indicate that other links are in the Disable state in the association request frame; (b) Non-AP MLD According to whether the association is successful, the capabilities of each AP MLD, and the link quality between the Non-AP MLD and each AP MLD, determine the target AP MLD, that is, determine which AP MLD is ultimately associated with; (c) Non-AP MLD sends EAP- Start to trigger processes such as 802.1X authentication with the target AP MLD, and four-way handshake to derive PTK and GTK.
  • Multi-link Association Multi-link Association
  • Non-AP MLD directly initiates tentative associations with multiple AP MLDs at the same time.
  • Select one AP MLD among multiple AP MLDs to perform processes such as 802.1X authentication, four-way handshake derivation of PTK and GTK. It can improve the association success rate of Non-AP MLD in the initial association process, and increase the association speed by initiating tentative associations in parallel (simultaneously).
  • FIG. 13c is another schematic diagram of interaction between Non-AP MLD and AP MLD in the initial association process provided by an embodiment of the present application.
  • three AP MLDs and one Non-AP MLD are taken as an example to describe the initial association method provided in the embodiment of the present application.
  • the initial association method includes: (A) Non-AP MLD sends a multi-link association request frame on multiple links (such as link 1, link 2, and link 3 in Figure 13c), and simultaneously communicates with multiple links.
  • Each AP MLD (AP MLD1, AP MLD2, and AP MLD3 in Figure 13c) initiates a tentative association, and indicates that other links are in the Disable state in the association request frame, and then performs 802.1X authentication with each AP MLD, four steps The handshake derives processes such as PTK and GTK;
  • Non-AP MLD triggers the target AP to send DS-STA-Notify.request primitives to notify the distributed system of corresponding STA-AP mapping information by sending STA-AP Mapping Notify frames.
  • Non-AP MLD directly initiates a tentative association with multiple AP MLDs at the same time, and performs 802.1X authentication with each AP MLD, four steps
  • the handshake derives processes such as PTK and GTK, and finally selects an AP MLD from the multiple AP MLDs, and sends a STA-AP Mapping Notify frame to it to trigger the target AP MLD to send the DS-STA-Notify.request primitive, which can improve Non -AP MLD's association success rate during the initial association process.
  • the embodiment of the present application also provides an association method applied to non-collocated multi-link devices in a non-AP MLD roaming scenario.
  • the following describes the method for associating non-co-located multi-link devices provided in the embodiments of the present application in conjunction with the optimal association scenario of Non-AP MLD.
  • Non-AP MLD includes two STAs, namely STA1 and STA2
  • AP MLD includes two APs, namely AP1 and AP2; one link or AP of AP MLD can work in the 2.4GHz frequency band, and the other A link or AP can work in the 5GHz frequency band.
  • the number of STAs included in Non-AP MLD may be more than two, and the number of APs included in AP MLD may also be more than two.
  • the number of STAs included is more than two and In the case where the number of APs included in the AP MLD is more than two, reference may be made to the description of two STAs and two APs in the embodiment of the present application, which will not be repeated here.
  • FIG. 14 is a schematic diagram of an optimal association scenario in a Non-AP MLD movement process provided by an embodiment of the present application.
  • the two STAs of the Non-AP MLD are associated with the two APs of the AP MLD1.
  • the two STAs of Non-AP MLD can associate with APs MLD1 and AP MLD2 working in the 2.4GHz frequency band, and establish A Non-Collocated MLD3, Non-Collocated MLD3 includes AP MLD1 and AP MLD2 AP working in the 2.4GHz frequency band.
  • the two STAs of Non-AP MLD associate with the two APs of AP MLD2.
  • FIG. 15 is a schematic flowchart of a method for associating a non-co-located multi-link device according to an embodiment of the present application.
  • the association method of the non-co-located multi-link device includes but is not limited to the following steps:
  • Non-AP MLD sends a multi-link association request frame to AP MLD2.
  • the AP MLD2 sends a multi-link setup request (MLD Setup Request) to the AP MLD1.
  • MLD Setup Request multi-link setup request
  • the AP MLD1 returns a multi-link setup response (MLD Setup Response) to the AP MLD2.
  • MLD Setup Response multi-link setup response
  • AP MLD2 returns a multi-link association response frame to Non-AP MLD.
  • FIG. 16 is a schematic diagram of interaction between Non-AP MLD and AP MLD provided by an embodiment of the present application.
  • AP MLD1 includes AP11 and AP12
  • AP MLD2 includes AP21 and AP22
  • Non-AP MLD includes STA1 and STA2.
  • AP11 and AP22 can work in the 5GHz frequency band
  • AP12 and AP22 can work in the 2.4GHz frequency band
  • CH1@2.4GHz means channel 1 of the 2.4GHz frequency band
  • CH1@5GHz means channel 1 of the 5GHz frequency band
  • CH2@ 2.4GHz means channel 2 of the 2.4GHz frequency band
  • CH2@5GHz means channel 2 of the 5GHz frequency band.
  • Non-AP MLD -STA1 of AP MLD sends Multi-link Association Request to AP MLD2; AP22 of AP MLD2 sends MLD Setup Request to AP12 of AP MLD1, requesting the establishment of a Non-collocated MLD3; AP12 of AP MLD1 returns MLD Setup Response to AP22 of AP MLD2 , Used to respond to MLD Setup Request; AP MLD2 returns Multi-link Association Response to STA1 of Non-AP MLD, used to respond to Multi-link Association Request.
  • the manner in which the MLD Setup Response responds to the MLD Setup Request includes approval or rejection. If the MLD Setup Response indicates that it agrees to establish a Non-collocated MLD3, AP22 and AP12 can share a high MAC layer, or AP22 and AP12 form a new logical multi-link device (ie Non-collocated MLD3). In the subsequent configuration process, AP22 and AP12 can be assigned a unified serial number, PTK, etc. It is understandable that in this scenario, Non-AP MLD can be regarded as switching from AP MLD1 to Non-collocated MLD3.
  • step S201 and step S204 in the embodiment of the present application can refer to the implementation manners of step S101 and step S102 in the first embodiment of the present application, which will not be repeated here.
  • the following information may be carried in the multi-link establishment request: non-AP MLD related information of STA1 and Non-collocated MLD3 related information.
  • the following information can be carried in the multi-link establishment response: Status code and Non-collocated MLD3 related information.
  • AP22 and AP11 negotiate non-collocated MLD3 related information through a multi-link establishment request and a multi-link establishment response.
  • the related information of STA1 may include SAP MAC Address of STA1, MAC Address indication of STA1, Anchor link indication, etc.
  • the related information of the non-collocated MLD3 may include the SAP MAC Address of the non-collocated MLD3, the link information corresponding to the AP22 of the AP MLD2, and the link information corresponding to the AP12 of the AP MLD1.
  • the link information corresponding to AP22 of AP MLD2 may include link identifier (Link ID), operating class (Operating class), channel number (Channel number), basic service set identifier (BSSID), and Other related information of AP22; the link information corresponding to AP12 of AP MLD1 may include Link ID, Operating class, Channel number, BSSID, etc.
  • the link information corresponding to AP22 of AP MLD2 may include Link ID, Operating class, Channel number, BSSID, etc.; the link information corresponding to AP12 of AP MLD1 may include Link ID, Operating class, Channel number, etc. , BSSID and other related information of AP 12.
  • the embodiment of this application establishes Non-collocated MLD3 through multi-link establishment request and response, so as to realize the association between Non-AP MLD and Non-collocated MLD3.
  • the embodiments of the present application also provide corresponding devices or equipment.
  • the embodiments of the present application can divide the functional modules of the site multi-link device or the access point multi-link device according to the foregoing method examples.
  • each functional module can be divided corresponding to each function, or two or more
  • the functions are integrated in a processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 17 is a schematic structural diagram of a communication device provided in an embodiment of the present application.
  • the communication device 1 may be a chip in Non-AP MLD or Non-AP MLD, such as a Wi-Fi chip.
  • the communication device 1 includes: a processing unit 11 and a transceiver unit 12.
  • the processing unit 11 is used to generate a multi-link association request frame; the transceiver unit 12 is used to send a multi-link association request frame to one or more second APs MLD, and the multi-link association request frame is used to initiate a non-AP Multi-link tentative association between the MLD and one or more second AP MLD; the transceiver unit 12 is also used to successfully associate the non-AP MLD with one or more second AP MLD multi-link tentative association
  • the foregoing transceiver unit 12 is further configured to send link state indication information to the first AP MLD, where the link state indication information is used to indicate that one or more first STAs of the Non-AP MLD and The state of the link between the first AP and MLD is the disconnected state.
  • the communication device 1 in the embodiment of the present application has any function of the Non-AP MLD in the foregoing method, and details are not described herein again.
  • FIG. 18 is another schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 2 may be a target AP MLD or a chip in the target AP MLD, such as a Wi-Fi chip.
  • the communication device 2 includes: a transceiver unit 21 and a processing unit 22.
  • the transceiver unit 21 is configured to receive a multi-link association request frame from the Non-AP MLD, and the multi-link association request frame is used to request the Non-AP MLD to perform multi-link tentative association with the target AP MLD; the transceiver unit 21 It is also used to receive indication information from the Non-AP MLD when the multi-link association response frame returned by the target AP MLD indicates that the association is successful, and the indication information is used to trigger the target AP MLD to update the mapping relationship between the site and the access point; The unit 22 is used for generating the mapping information between the station and the access point; the transceiver unit 21 is also used for sending the mapping information between the station and the access point, and the mapping information between the station and the access point is used to indicate the station and the access point The mapping relationship of is updated from the association of Non-AP MLD with the first AP MLD to the association of Non-AP MLD with the target AP MLD.
  • the communication device 2 in the embodiment of the present application has any function of the target AP MLD in the foregoing method, and details are not described herein again.
  • Non-AP MLD and the target AP MLD described in the embodiments of this application can be implemented by a general bus architecture.
  • Non-AP MLD includes a processor and a transceiver internally connected and communicated with the processor.
  • the processor is used to generate a multi-link association request frame
  • the transceiver is used to send a multi-link association request frame to one or more second AP MLDs
  • the multi-link association request frame is used to initiate Non-AP MLD and one Or multi-link tentative associations between multiple second APs MLDs
  • the transceiver is also used in the case where the non-AP MLDs and one or more second APs MLD’s multi-link tentative associations are successful
  • Sending indication information to the target AP MLD is used to trigger the target AP MLD to update the mapping relationship between the site and the access point, and the target AP MLD is a second AP MLD determined from one or more second AP MLDs.
  • the Non-AP MLD may further include a memory, and the memory is used to store instructions executed by the processor.
  • the target AP MLD includes a processor and a transceiver internally connected and communicated with the processor.
  • the transceiver is used to receive a multi-link association request frame from the Non-AP MLD, and the multi-link association request frame is used to request the Non-AP MLD to perform multi-link tentative association with the target AP MLD; the transceiver also It is used to receive indication information from the Non-AP MLD when the multi-link association response frame returned by the target AP MLD indicates that the association is successful.
  • the indication information is used to trigger the target AP MLD to update the mapping relationship between the station and the access point.
  • the device is used to generate the mapping information between the station and the access point, and the transceiver is also used to send the mapping information between the station and the access point.
  • the mapping information between the station and the access point is used to indicate the mapping relationship between the station and the access point.
  • the association between Non-AP MLD and the first AP MLD is updated to Non-AP MLD and the target AP MLD association.
  • the target AP MLD may further include a memory, and the memory is used to store instructions executed by the processor.
  • Non-AP MLD and the target AP MLD described in the embodiments of this application can be implemented by a general-purpose processor.
  • a general-purpose processor implementing Non-AP MLD includes a processing circuit and an input and output interface for internal connection and communication with the processing circuit.
  • the processing circuit is used to generate a multi-link association request frame
  • the input and output interface is used to send a multi-link association request frame to one or more second APs MLD
  • the multi-link association request frame is used to initiate a non-AP Multi-link tentative association between the MLD and one or more second AP MLD
  • this input and output interface is also used for the successful multi-link tentative association between the Non-AP MLD and one or more second AP MLD
  • the target AP MLD is the second AP MLD determined from one or more second AP MLDs .
  • the general-purpose processor may further include a storage medium for storing instructions executed by the processing circuit.
  • a general-purpose processor for achieving the target AP MLD includes a processing circuit and an input and output interface for internal connection and communication with the processing circuit.
  • the input and output interface is used to receive the multi-link association request frame from the Non-AP MLD, and the multi-link association request frame is used to request the non-AP MLD to perform multi-link tentative association with the target AP MLD;
  • the input and output interface It is also used to receive indication information from the Non-AP MLD when the multi-link association response frame returned by the target AP MLD indicates that the association is successful, and the indication information is used to trigger the target AP MLD to update the mapping relationship between the site and the access point;
  • the processing circuit is used to generate the mapping information between the station and the access point;
  • the input and output interface is also used to send the mapping information between the station and the access point, and the mapping information between the station and the access point is used to indicate the station and the access point.
  • the mapping relationship is updated from the association of Non-AP MLD with the first AP MLD
  • Non-AP MLD and target AP MLD described in the embodiments of this application can also be implemented using the following: one or more FPGAs (Field Programmable Gate Array), PLD (Programmable Logic) Devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.
  • FPGAs Field Programmable Gate Array
  • PLD Programmable Logic
  • the embodiments of the present application also provide a computer-readable storage medium in which computer program code is stored.
  • the electronic device executes the method in any of the foregoing embodiments.
  • the embodiments of the present application also provide a computer program product, which when the computer program product runs on a computer, causes the computer to execute the method in any of the foregoing embodiments.
  • the embodiments of the present application also provide a communication device, which may exist in the form of a chip product.
  • the structure of the device includes a processor and an interface circuit.
  • the processor is used to communicate with other devices through a receiving circuit so that the device executes the foregoing The method in any embodiment.
  • An embodiment of the present application also provides a wireless communication system, including at least one site multi-link device and at least two access point multi-link devices.
  • the site multi-link device and the access point multi-link device can perform any of the foregoing.
  • the method in one embodiment.
  • the steps of the method or algorithm described in conjunction with the disclosure of the present application can be implemented in a hardware manner, or can be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (Random Access Memory, RAM), flash memory, erasable programmable read-only memory (Erasable Programmable ROM, EPROM), and electrically erasable Programming read-only memory (Electrically EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the functions described in this application can be implemented by hardware, software, firmware, or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer-readable storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Landscapes

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

Abstract

本申请涉及无线通信领域，尤其涉及一种多链路试关联方法及相关装置，比如应用于支持802.11be标准的无线局域网中。该方法包括：Non-AP MLD中与第一AP MLD之间的链路状态为断开状态的第一STA，生成并向第二AP MLD发送多链路关联请求帧，用于请求Non-AP MLD与第二AP MLD进行多链路试探性关联；在关联成功的情况下，Non-AP MLD发送指示信息，用于触发第二AP MLD更新站点与接入点的映射关系，可以实现多链路设备在进行漫游时，减少漫游过程中数据传输的中断时间，并且可以通过控制更新站点与接入点的映射信息的时机使得漫游过程中的数据传输不中断。

Description

多链路试关联方法及相关装置
本申请要求于2020年5月27日提交中国专利局、申请号为202010463544.7、申请名称为“多链路试关联方法及相关装置”的中国专利申请的优先权，以及2020年6月16日提交中国专利局、申请号为202010550151.X、申请名称为“多链路试关联方法及相关装置”的中国专利申请的优先权；以上专利申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种多链路试关联方法及相关装置。
背景技术
无线局域网(wireless local area network，WLAN)漫游或Wi-Fi漫游是指无线终端或站点(station，STA)从一个接入点(access point，AP)转移到另一个AP，即该无线终端或该STA从一个基本服务集(basic service set，BSS)移动接入到另一个BSS的过程。WLAN漫游或Wi-Fi漫游过程中，STA可以在属于同一扩展服务集(extended service set，ESS)内的Wi-Fi网络中任意移动，如从同一个ESS中的一个BSS切换到另一个BSS；并且通过用户的标识(互联网协议(internet protocol，IP)地址)不改变，即客户端在连接网络初期获得的IP地址在整个漫游过程中不改变，来实现业务不中断(即客户端的业务不中断)。
当STA从一个AP漫游到另外一个AP时，首先会断开与原AP的连接，在与新AP的连接建立完成之前，AP和STA之间无法进行业务数据传输。因此，为了减少漫游过程中数据传输的中断时间，即减少漫游时延(漫游时延是指从STA与原AP断开连接开始到可以与新AP进行数据传输为止的时间)，可通过成对主秘钥(pairwise master key，PMK)缓存来实现。参见图1，图1是使用PMK缓存实现STA快速漫游的示意图。如图1所示，在漫游之前，STA与原AP(图1中的AP1)通过用户关联、802.1X认证过程、单播组播秘钥(key)协商以及加密数据报文通讯等完成STA与原AP的整个关联协商。在STA与原AP的单播组播秘钥(key)协商过程中，STA会缓存PMK和/或PMK标识(即PMKID)，接入点控制器(AP controller，AC)也会缓存PMK和/或PMKID。当STA进行漫游时，STA向新AP(图1中的AP2)发起重关联，该重关联携带STA缓存的PMKID；新AP接收到PMKID之后，将该PMKID发送给AC；AC通过新AP发送的该PMKID查找本地是否存储有相同的PMKID信息，如果有，说明该STA之前已经通过802.1X认证，可以不需要再次进行802.1X认证，直接与新AP进行单播组播秘钥的派生。在单播组播秘钥(key)协商完成之后，STA可以利用此次协商的秘钥加密数据并与新AP进行报文通讯。
由此可知，使用PMK缓存的STA快速漫游机制通过缓存PMKID，使得STA在切换AP后直接跳过繁琐的802.1X认证过程，从而减少了漫游时延。但是，使用PMK缓存的STA快速漫游机制只能减少漫游过程中数据传输的中断时间，不能实现数据传输的不中断。其中，数据传输不中断是指在漫游过程(或从一个BSS切换到另一个BSS的过程，或从一个AP切换到另一个AP的过程)中，始终存在至少一条链路可以进行数据传输。
因此，由于下一代Wi-Fi标准IEEE 802.11be(Wi-Fi联盟称为Wi-Fi 7，又称为极高吞吐率(extremely high throughput，EHT)标准)的一个关键技术是多链路(multi-link)技术， 相应地，多链路技术需要多链路设备(multi-link device，MLD)来支撑，多链路设备是指同时具有多个射频模块，且该多个射频模块分别工作在不同频段或信道上的设备。所以对于多链路设备的漫游，有望实现数据传输的不中断。但是，如何实现IEEE 802.11be下多链路设备的漫游，减少漫游过程中数据传输的中断时间，或者使得漫游过程的数据传输不中断，尚未得到解决。
发明内容
本申请实施例提供一种多链路试关联方法及相关装置，可以实现IEEE 802.11be下多链路设备在进行漫游时，减少漫游过程中数据传输的中断时间，并且可以通过控制更新站点与接入点的映射信息的时机使得漫游过程中的数据传输不中断。
第一方面，本申请实施例提供一种多链路试关联方法，应用于非接入点多链路设备(Non-AP MLD)中，Non-AP MLD中包括多个STA，该多链路试关联方法包括：Non-AP MLD中与第一AP MLD之间的链路状态为断开状态的一个或多个第一STA，生成并向一个或多个第二AP MLD发送多链路关联请求帧，该多链路关联请求帧用于发起Non-AP MLD与一个或多个第二AP MLD之间的多链路试探性关联；Non-AP MLD接收一个或多个第二AP MLD返回的一个或多个多链路关联响应帧；如果该一个或多个多链路关联响应帧指示多链路试探性关联成功，则Non-AP MLD向目标AP MLD发送指示信息，用于触发目标AP MLD更新站点与接入点的映射关系，该目标AP MLD为从一个或多个第二AP MLD中确定出的第二AP MLD。
可选的，Non-AP MLD的第二STA与第一AP MLD之间的链路状态为连接状态。
可选的，Non-AP MLD从一个或多个第二AP MLD中确定出目标AP MLD的方式为：Non-AP MLD根据Non-AP MLD与多个第二AP MLD之间的关联是否成功、各个第二AP MLD的能力以及Non-AP MLD与各个第二AP MLD的链路质量，从该多个第二AP MLD中选择出一个最终的目标AP MLD。
本方案利用Non-AP MLD中与第一AP MLD之间的链路状态为断开状态的一个或多个STA，同时向一个或多个第二AP MLD发起多链路试探性关联，在关联成功后，发送一个指示信息，通知第二AP MLD可以更新站点与接入点的映射关系，以使来自Non-AP MLD的数据包可以正确递交到对应的AP MLD，实现IEEE 802.11be下多链路设备在进行漫游时，减少漫游过程中数据传输的中断时间，并且可以通过控制更新站点与接入点的映射信息的时机使得漫游过程中的数据传输不中断。
结合第一方面，在一种可能的设计中，Non-AP MLD的第一STA向第二AP MLD发送多链路关联请求帧之前，该方法还包括：Non-AP MLD可以向第一AP MLD发送链路状态指示信息，该链路状态指示信息用于指示Non-AP MLD的第一STA与第一AP MLD之间的链路状态为断开状态。
可选的，该链路状态指示信息还用于指示Non-AP MLD的第一STA与第一AP MLD之间的链路状态为断开状态的原因。
可选的，第一STA与第一AP MLD之间的链路状态为断开状态的原因为试探性关联。
本方案通过链路状态指示信息来告知第一AP MLD某条或某几条链路因为试探性关联 而断开，避免第一AP MLD因为待传输的数据量大，而尝试请求该某条或该某几条链路开启。
第二方面，本申请实施例提供一种多链路试关联方法，应用于目标AP MLD中，目标AP MLD中包括多个AP，该多链路试关联方法包括：目标AP MLD接收来自Non-AP MLD的多链路关联请求帧，该多链路关联请求帧用于请求Non-AP MLD与目标AP MLD进行多链路试探性关联；如果目标AP MLD返回的多链路关联响应帧指示关联成功，则目标AP MLD从Non-AP MLD接收指示信息，该指示信息用于触发目标AP MLD更新站点与接入点的映射关系；目标AP MLD接收到该指示信息后，发送站点与接入点的映射信息，该站点与接入点的映射信息用于指示站点与接入点的映射关系从Non-AP MLD与第一AP MLD关联更新为Non-AP MLD与目标AP MLD关联。
结合第二方面，在一种可能的设计中，站点与接入点的映射信息中包括Non-AP MLD的服务接入点SAP媒体接入控制MAC地址、和第二AP MLD的SAP MAC地址。
第三方面，本申请实施例提供一种通信装置，该通信装置可以为Non-AP MLD或Non-AP MLD中的芯片，比如Wi-Fi芯片，包括：
处理单元，用于生成多链路关联请求帧；收发单元，用于向一个或多个第二AP MLD发送多链路关联请求帧，该多链路关联请求帧用于发起Non-AP MLD与一个或多个第二AP MLD之间的多链路试探性关联；该收发单元，还用于在Non-AP MLD与一个或多个第二AP MLD的多链路试探性关联成功的情况下，向目标AP MLD发送指示信息，用于触发目标AP MLD更新站点与接入点的映射关系，该目标AP MLD为从一个或多个第二AP MLD中确定出的第二AP MLD。
可选的，第一STA与第一AP MLD之间的链路状态为断开状态、且Non-AP MLD的第二STA与第一AP MLD之间的链路状态为连接状态。
结合第三方面，在一种可能的设计中，上述收发单元还用于：向第一AP MLD发送链路状态指示信息，该链路状态指示信息用于指示Non-AP MLD的一个或多个第一STA与第一AP MLD之间的链路状态为断开状态。
可选的，该链路状态指示信息还用于指示第一STA与第一AP MLD之间的链路状态为断开状态的原因。
可选的，第一STA与第一AP MLD之间的链路状态为断开状态的原因为试探性关联。
第四方面，本申请实施例提供另一种通信装置，该通信装置可以为目标AP MLD或目标AP MLD中的芯片，比如Wi-Fi芯片，包括：
收发单元，用于接收来自Non-AP MLD的多链路关联请求帧，该多链路关联请求帧用于请求Non-AP MLD与目标AP MLD进行多链路试探性关联；该收发单元，还用于当目标AP MLD返回的多链路关联响应帧指示关联成功时，从Non-AP MLD接收指示信息，该指示信息用于触发目标AP MLD更新站点与接入点的映射关系；处理单元，用于生成站点与接入点的映射信息；该收发单元，还用于发送站点与接入点的映射信息，该站点与接入点的映射信息用于指示站点与接入点的映射关系从Non-AP MLD与第一AP MLD关联更新为Non-AP MLD与目标AP MLD关联。
结合第四方面，在一种可能的设计中，站点与接入点的映射信息中包括Non-AP MLD 的服务接入点SAP媒体接入控制MAC地址、和目标AP MLD的SAP MAC地址。
上述任一方面的一种实现方式中，上述指示信息可以携带于A-控制字段中，也可携带于通知帧中，如STA-AP Mapping Notify帧。
上述任一方面的一种实现方式中，上述多链路关联请求帧中可以包括Non-AP MLD与第二AP MLD之间的非传输链路的链路状态。
可选的，该多链路关联请求帧中还可以包括原因码字段，该原因码字段可以用于指示Non-AP MLD的第二STA与第二AP MLD之间的链路状态为断开状态的原因。其中，该原因码字段可以设置为“与旧AP MLD关联”。
本方案通过在多链路关联请求帧中携带Non-AP MLD与第二AP MLD之间的非传输链路的链路状态，可以避免第二AP MLD因为不知道Non-AP MLD与第二AP MLD之间的链路状态，而采用链路状态为断开状态的链路向Non-AP MLD传输数据。
上述任一方面的一种实现方式中，上述多链路关联请求帧中还可以包括试探性关联指示信息，用于指示本次关联操作是否为多链路试探性关联。
可选的，上述多链路关联请求帧还可以包括试探性关联生命期信息，用于指示该多链路试探性关联的生命周期。
可选的，该试探性关联指示信息和该试探性关联生命期信息携带于多链路聚合MLA元素的公共信息字段中。
本方案在多链路关联请求帧中携带试探性关联指示信息，来区分正常的多链路关联和多链路试探性关联；在通过携带试探性关联生命期信息，以使Non-AP MLD与AP MLD之间没有交互的时间超过该生命周期时，AP MLD删除之前与Non-AP MLD协商的信息，从而释放缓存空间。
第五方面，本申请实施例提供了一种通信装置，具体为Non-AP MLD，包括处理器，收发器，该处理器被配置为支持Non-AP MLD执行上述第一方面的方法中相应的功能。该收发器用于支持Non-AP MLD与AP MLD之间的通信，向AP MLD发送上述方法中所涉及的信息，帧，数据分组或者指令等。该Non-AP MLD还可以包括存储器，该存储器用于与处理器耦合，其保存Non-AP MLD必要的程序指令和数据。
具体地，该处理器用于生成多链路关联请求帧；该收发器用于向一个或多个第二AP MLD发送多链路关联请求帧，该多链路关联请求帧用于发起Non-AP MLD与一个或多个第二AP MLD之间的多链路试探性关联；该收发器，还用于在Non-AP MLD与一个或多个第二AP MLD的多链路试探性关联成功的情况下，向目标AP MLD发送指示信息，用于触发目标AP MLD更新站点与接入点的映射关系，该目标AP MLD为从一个或多个第二AP MLD中确定出的第二AP MLD。
第六方面，本申请实施例提供了一种通信装置，具体为目标AP MLD，包括处理器，收发器，该处理器被配置为支持目标AP MLD执行上述第二方面的方法中相应的功能。该收发器用于支持目标AP MLD与Non-AP MLD之间的通信，向Non-AP MLD发送上述方法中所涉及的信息，帧，数据分组或者指令等。该AP MLD还可以包括存储器，该存储器用于与处理器耦合，其保存AP MLD必要的程序指令和数据。
具体地，该收发器用于接收来自Non-AP MLD的多链路关联请求帧，该多链路关联请 求帧用于请求Non-AP MLD与目标AP MLD进行多链路试探性关联；该收发器，还用于当目标AP MLD返回的多链路关联响应帧指示关联成功时，从Non-AP MLD接收指示信息，该指示信息用于触发目标AP MLD更新站点与接入点的映射关系；该处理器用于生成站点与接入点的映射信息；该收发器，还用于发送站点与接入点的映射信息，该站点与接入点的映射信息用于指示站点与接入点的映射关系从Non-AP MLD与第一AP MLD关联更新为Non-AP MLD与目标AP MLD关联。
第七方面，本申请实施例提供一种无线通信系统，该系统包括上述第三方面或上述第五方面所述的Non-AP MLD，以及，上述第四方面或上述第六方面所述的目标AP MLD。
第八方面，本申请实施例提供一种芯片或芯片系统，包括输入输出接口和处理电路，该处理电路用于生成多链路关联请求帧；该输入输出接口用于向一个或多个第二AP MLD发送多链路关联请求帧，该多链路关联请求帧用于发起Non-AP MLD与一个或多个第二AP MLD之间的多链路试探性关联；该输入输出接口，还用于在Non-AP MLD与一个或多个第二AP MLD的多链路试探性关联成功的情况下，向目标AP MLD发送指示信息，用于触发目标AP MLD更新站点与接入点的映射关系，该目标AP MLD为从一个或多个第二AP MLD中确定出的第二AP MLD。
在一种可能的设计中，该输入输出接口用于接收来自Non-AP MLD的多链路关联请求帧，该多链路关联请求帧用于请求Non-AP MLD与目标AP MLD进行多链路试探性关联；该输入输出接口，还用于当目标AP MLD返回的多链路关联响应帧指示关联成功时，从Non-AP MLD接收指示信息，该指示信息用于触发目标AP MLD更新站点与接入点的映射关系；该处理电路用于生成站点与接入点的映射信息；该输入输出接口，还用于发送站点与接入点的映射信息，该站点与接入点的映射信息用于指示站点与接入点的映射关系从Non-AP MLD与第一AP MLD关联更新为Non-AP MLD与目标AP MLD关联。
第九方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述任一方面所述的多链路试关联方法。
第十方面，本申请提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一方面所述的多链路试关联方法。
实施本申请实施例，可以实现IEEE 802.11be下多链路设备在进行漫游时，减少漫游过程中数据传输的中断时间，并且可以通过控制更新站点与接入点的映射信息的时机使得漫游过程中的数据传输不中断。
附图说明
图1是使用PMK缓存实现STA快速漫游的示意图；
图2是本申请实施例提供的无线通信系统的一架构示意图；
图3是本申请实施例提供的多链路设备的一结构示意图；
图4是AP多链路设备与Non-AP多链路设备连接的一示意图；
图5是本申请实施例提供的多链路试关联方法的一示意流程图；
图6a是本申请实施例提供的一个新元素的帧结构示意图；
图6b是本申请实施例提供的另一个新元素的帧结构示意图；
图7a是本申请实施例提供邻居汇报元素的一种帧结构示意图；
图7b是本申请实施例提供精简的邻居汇报元素的一种帧结构示意图；
图7c是本申请实施例提供的12字节的TBTT信息长度字段的一种帧结构示意图；
图8是本申请实施例提供的Non-APMLD与一个APMLD进行802.1X认证和四步握手派生PTK和GTK的交互示意图；
图9a是本申请实施例提供的BSS转移管理询问帧的部分或全部帧结构的示意图；
图9b是本申请实施例提供的BSS转移管理请求帧的部分或全部帧结构的示意图；
图9c是本申请实施例提供的BSS转移管理响应帧的部分或全部帧结构的示意图；
图10是本申请实施例提供的Non-AP MLD在漫游过程中切换AP MLD的一示意图；
图11是本申请实施例提供的Non-AP MLD在漫游过程中切换AP MLD的信令交互示意图；
图12a是本申请实施例提供的不同状态间的转换关系和不同状态下所允许发送的帧类型的一示意图；
图12b是本申请实施例提供的不同状态间的转换关系和不同状态下所允许发送的帧类型的另一示意图；
图13a是本申请实施例提供的初始关联过程中Non-AP MLD与AP MLD的一交互示意图；
图13b是本申请实施例提供的初始关联过程中Non-AP MLD与AP MLD的另一交互示意图；
图13c是本申请实施例提供的初始关联过程中Non-AP MLD与AP MLD的又一交互示意图；
图14是本申请实施例提供的Non-APMLD移动过程中的最优关联场景示意图；
图15是本申请实施例提供的非共址多链路设备的关联方法的一示意流程图；
图16是本申请实施例提供的Non-AP MLD与AP MLD的一交互示意图；
图17是本申请实施例提供的通信装置的一结构示意图；
图18是本申请实施例提供的通信装置的另一结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
为更好地理解本申请实施例的提供的多链路试关联方法，下面将对本申请实施例提供的多链路试关联方法的系统架构和/或应用场景进行说明。可理解的，本申请实施例描述的场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定。
本申请实施例提供一种应用于无线通信系统的多链路试关联方法，可以实现IEEE802.11be下多链路设备在进行漫游时，减少漫游过程中数据传输的中断时间，并且可以通过控制更新站点与接入点的映射信息的时机使得漫游过程中的数据传输不中断。该无线通 信系统可以为无线局域网，该多链路试关联方法可以由无线通信系统中的通信设备或通信设备中的芯片或处理器实现，该通信设备可以是一种支持多条链路并行传输的无线通信设备，例如，该通信设备可以称为多链路设备或多频段设备(multi-band device)。可选的，根据多链路设备的射频(Radio)个数，又分为单Radio多链路设备和多Radio多链路设备。
多射频(Radio)多链路设备包括多个隶属的站点(affiliated STA)。其中，隶属的站点可以为接入点(access point，AP)或非接入点站点(non-access point station，non-AP STA)。为描述方便，本申请将隶属的站点为AP的多链路设备可以称为多链路AP或多链路AP设备或AP多链路设备(AP multi-link device，AP MLD)，隶属的站点为non-AP STA的多链路设备可以称为多链路Non-AP或多链路Non-AP设备或Non-AP多链路设备(Non-AP multi-link device，Non-AP MLD)。为描述方便，“多链路设备包括隶属的站点”在本申请实施例中也简要描述为“多链路设备包括站点”。
下文提到的链路标识用于表征AP MLD在某个频段的某个信道上建立的基本服务集，即(操作类别(Operating Class),信道号(channel number)，基本服务集标识(BSSID))。Non-AP MLD通过某个隶属的STA通过一次关联操作来实现Non-AP MLD的多个隶属STA同时与AP MLD的不同AP分别进行关联来建立多条传输链路。Non-AP MLD和AP MLD可以通过链路标识来指示对应的链路以及链路两端所对应的AP和Non-AP STA。因此，在Non-AP MLD与AP MLD之间进行相关信令指示时，只需携带对应的链路标识，减少了信令开销。
一个示例中，AP多链路设备在建立BSS时，发送的管理帧，比如beacon帧，会携带包括多个链路标识信息字段的元素。每个链路标识信息字段包括链路标识，还包括：BSS标识符，操作类别，信道号中的一个或多个，其中BSS标识符，操作集，信道号中的一个或多个与链路标识相对应。另一个示例中，在建立多链路关联的过程中，AP MLD和Non-AP MLD协商多个链路标识信息字段。在后续的通信中，AP MLD或者Non-AP MLD会通过使用链路标识来表征对应链路两端的站点。
多链路设备可以遵循IEEE 802.11系列协议实现无线通信，例如，遵循极高吞吐率的站点，或遵循基于IEEE 802.11be或兼容支持IEEE 802.11be的站点，实现与其他设备的通信。
本申请实施例提供的多链路试关联方法可以应用于无线通信系统的多链路设备漫游场景中，如至少一个Non-AP多链路设备在至少两个AP多链路设备之间漫游的场景中，或者至少一个Non-AP多链路设备从同一个ESS中的一个BSS切换到另一个BSS的场景中。
参见图2，图2是本申请实施例提供的无线通信系统的一架构示意图。如图2所示，该无线通信系统包括：多个AP多链路设备(如图2中的AP多链路设备100和AP多链路设备200)，和一个Non-AP多链路设备300。其中，该AP多链路设备是为Non-AP多链路设备提供服务的多链路设备，Non-AP多链路设备可以与AP多链路设备之间采用多条链路进行通信，从而达到提升吞吐率的效果。图2中AP多链路设备和Non-AP多链路设备的个数，仅是示例性的。
示例性的，多链路设备(如图2的AP多链路设备100、AP多链路设备200、Non-AP多链路设备300中的任一多链路设备)为具有无线通信功能的装置，该装置可以为一个整 机的设备，还可以是安装在整机设备中的芯片或处理系统等，安装这些芯片或处理系统的设备可以在这些芯片或处理系统的控制下，实现本申请实施例的方法和功能。例如，本申请实施例中的Non-AP多链路设备具有无线收发功能，可以支持802.11系列协议，可以与AP多链路设备或其他Non-AP多链路设备进行通信。例如，Non-AP多链路设备是允许用户与AP通信进而与WLAN通信的任何用户通信设备。例如，Non-AP多链路设备可以为平板电脑、桌面型、膝上型、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、手持计算机、上网本、个人数字助理(personal digital assistant，PDA)、手机等可以联网的用户设备，或物联网中的物联网节点，或车联网中的车载通信装置等；Non-AP多链路设备还可以为上述这些终端中的芯片和处理系统。本申请实施例中的AP多链路设备为Non-AP多链路设备提供服务的装置，可以支持802.11系列协议。例如，AP多链路设备可以为通信服务器、路由器、交换机、网桥等通信实体，或，AP多链路设备可以包括各种形式的宏基站，微基站，中继站等，当然AP多链路设备还可以为这些各种形式的设备中的芯片和处理系统，从而实现本申请实施例的方法和功能。
可理解的，多链路设备可以支持高速率低时延的传输，随着无线局域网应用场景的不断演进，多链路设备还可以应用于更多场景中，比如为智慧城市中的传感器节点(比如，智能水表，智能电表，智能空气检测节点)，智慧家居中的智能设备(比如智能摄像头，投影仪，显示屏，电视机，音响，电冰箱，洗衣机等)，物联网中的节点，娱乐终端(比如AR，VR等可穿戴设备)，智能办公中智能设备(比如，打印机，投影仪等)，车联网中的车联网设备，日常生活场景中的一些基础设施(比如自动售货机，商超的自助导航台，自助收银设备，自助点餐机等)。本申请实施例中对于Non-AP多链路设备和AP多链路设备的具体形式不做限定，在此仅是示例性说明。其中，802.11协议可以为支持802.11be或兼容802.11be的协议。
可选的，参见图3，图3是本申请实施例提供的多链路设备的一结构示意图。IEEE 802.11标准关注多链路设备中的802.11物理层(physical layer，PHY)和MAC层部分。如图3所示，多链路设备中包括的多个STA共享一个高MAC(high MAC)层，但低MAC(low MAC)层和PHY层互相独立。可理解的，多链路设备包括的多个STA也可以在低MAC层和PHY层互相独立，在高MAC层也互相独立。本申请实施例对于多链路设备的内部结构示意图并不进行限定，图3仅是示例性说明。示例性的，该高MAC层或低MAC层都可以由多链路设备的芯片系统中的一个处理器实现，还可以分别由一个芯片系统中的不同处理模块实现。
在本申请的实施例中，多链路设备可以允许同一业务标识符(traffic identifier，TID)的业务在不同链路上同时传输，甚至允许相同的数据包在不同链路上传输；也可以不允许同一TID的业务在不同链路上传输，但允许不同TID的业务在不同的链路上传输。
多链路设备工作的频段可以包括sub 1GHz、2.4GHz、5GHz、6GHz以及高频60GHz中的一个或多个频段。
可选的，参见图4，图4是AP多链路设备与Non-AP多链路设备连接的一示意图。如图4所示，Non-AP多链路设备和AP多链路设备都采用高MAC层共用的结构，AP多链路设备包括两个AP，Non-AP多链路设备包括两个STA。AP多链路设备中的一个AP可以与 Non-AP多链路设备中的一个STA建立一个链路进行通信，例如，图4的AP多链路设备中AP1与Non-AP多链路设备中STA1建立链路1进行通信；图4的AP多链路设备中AP2与Non-AP多链路设备中STA2建立链路2进行通信。
上述内容阐述了本申请实施例提供的多链路试关联方法的系统架构和/或应用场景，下面将结合附图对本申请实施例提供的多链路通信方法进行详细说明。
在一些可行的实施方式中，本申请实施例提及的Non-AP多链路设备可以为图2中的Non-AP多链路设备300，第一AP多链路设备可以为图2中的AP多链路设备100，第二多链路设备可以为图2中的AP多链路设备200。可理解的，本申请实施例中的Non-AP多链路设备也可以称为STA多链路设备，故Non-AP多链路设备与STA多链路设备可以相互替换使用。
在一些可行的实施方式中，本申请实施例中的多链路设备均支持在多条链路上同时发送和接收(simultaneous transmit and receive，STR)，或者本申请实施例的多链路设备具备STR能力。具备STR能力的多链路设备是指多链路设备内的任两个射频模块所工作的信道间距足够大，使得该任两个射频模块可以相互不干扰，可以独立的运行，支持在一条链路上发送的同时，另一条链路上可以正常接收。
实施例一
本申请实施例提供一种多链路试关联方法，利用Non-AP MLD可同时工作的多个radio/link，同时与多个AP MLD进行试探性关联，从而实现多链路设备在进行漫游时数据传输不中断或者减少数据传输的中断时间。
参见图5，图5是本申请实施例提供的多链路试关联方法的一示意流程图。如图5所示，本申请实施例提供的多链路试关联方法包括但不限于以下步骤：
S101，在Non-AP MLD与第一AP MLD之间的部分链路的状态为断开状态(或disable)的情况下，Non-AP MLD的一个或多个第一STA向一个或多个第二AP MLD分别发送多链路关联请求帧，该多链路关联请求帧用于请求Non-AP MLD与一个或多个第二AP MLD进行多链路试探性关联。其中第一STA与第一AP MLD之间的链路状态为断开状态(或disable)，Non-AP MLD的一个或多个第二STA与第一AP MLD之间的链路状态为连接状态(或enable)。
S102，一个或多个第二AP MLD向Non-AP MLD返回多链路关联响应帧。
具体地，在Non-AP MLD与第一AP MLD之间只有一条Disable链路的情况下，即在Non-AP MLD中只有一个第一STA的情况下，Non-AP MLD中与第一AP MLD之间的链路状态为Disable的第一STA向一个第二AP MLD发送多链路关联请求帧。在Non-AP MLD与第一AP MLD之间存在多条disable链路的情况下，即在Non-AP MLD中存在多个第一STA的情况下，Non-AP MLD的任一第一STA均可以向一个第二AP MLD发送多链路关联请求帧。可理解的，在Non-AP MLD中存在多个第一STA的情况下，Non-AP MLD的多个第一STA可以向多个第二AP MLD发送多链路关联请求帧。相应地，一个或多个第二AP MLD向Non-AP MLD返回多链路关联响应帧。
可选的，多链路关联请求(multi-link Association Request)帧中可以包括Non-AP MLD 与第二AP MLD之间非传输链路的状态，如disable或enable。可选的，当状态为Disable时，多链路关联请求帧中还可以携带原因码(Reason Code)字段，用于指示Non-AP MLD与第二AP MLD之间的链路状态为disable的原因。具体地，如果Non-AP MLD与第二AP MLD之间的某条链路的状态为disable状态，则可以进一步通过Reason Code字段指示该条链路的状态为disable的原因是节能、低接收信号强度指示、试探性关联以及与第一AP MLD关联(即“与旧AP MLD关联(Associated with old AP MLD)”)中的一种。本申请实施例中多链路关联请求帧中携带的Reason Code字段可以设置为“与旧AP MLD关联”。
可选的，对于Non-AP MLD来说，可以通过在某条链路上进行多链路关联操作来实现与AP MLD的多条链路同时建立关联。其中，进行多链路关联请求/响应帧交互的链路称之为传输链路(Transmitted Link)，相应的其他链路称之为非传输链路(Non-transmitted Link)。
可选的，如果第二AP MLD中的AP也可以关闭，则多链路关联响应帧也可以指示第二AP MLD中的每个AP是disable状态还是enable状态。
可选的，Non-AP MLD与第二AP MLD之间非传输链路的状态也可以通过TID-to-link映射(TID-to-link mapping)来隐式指示。该TID-to-link mapping可以携带于多链路关联请求/响应帧中，也可以在多链路关联请求/响应帧交互完成后，单独发送一个TID-to-mapping请求，用来指示Non-AP MLD与第二AP MLD之间非传输链路的状态。
可选的，多链路关联请求(multi-link Association Request)帧可以携带试探性关联(Tentative Association)指示信息，可选的，还可以携带试探性关联生命周期(Tentative Association lifetime)信息。其中，Tentative Association指示信息可以用于指示是否进行试探性关联，例如，携带试探性关联指示信息的字段置1，表示进行试探性关联；携带试探性关联指示信息的字段置0，表示进行现有协议定义的正常关联。可理解的，本申请实施例对携带试探性关联指示信息的字段的取值和含义不做限定。Tentative Association lifetime信息可以用于指示试探性关联的生命周期，当Non-AP MLD与AP MLD之间没有交互的时间超过该生命周期时，AP MLD删除之前与该Non-AP MLD协商的信息。Tentative Association指示信息和Tentative Association lifetime信息可以携带在多链路关联请求帧的多链路聚合(multi-link aggregation，MLA)元素中的公共信息字段中。可选的，Tentative Association指示信息和Tentative Association lifetime信息也可以携带于一个新定义的元素中。参见图6a，图6a是本申请实施例提供的一个新元素的帧结构示意图。如图6a所示，该元素的帧结构包括元素标识、长度、控制字段以及试探性关联生命期。其中，控制字段中用1比特来指示是否进行试探性关联，其余7比特预留。
可选的，多链路关联请求帧可以携带试探性关联控制字段和试探性关联生命周期。其中试探性关联控制字段中包括三个指示比特，分别是Non-AP MLD触发802.1X认证指示位、Non-AP MLD触发四步握手指示位和Non-AP MLD触发STA-AP映射通知指示位。具体地，当Non-AP MLD触发802.1X认证指示位置1时，表示Non-AP MLD会主动发送消息来触发802.1X认证流程的开始；当Non-AP MLD触发四步握手指示位置1时，表示Non-AP MLD会主动发送消息来触发四步握手流程的而开始；当Non-AP MLD触发STA-AP映射通知指示位置1时，表示Non-AP MLD会主动发送消息来触发STA-AP映射通知。可理解的，上述试探性关联控制字段包括的3个指示位的取值与含义不做限定。试探性关联 生命周期信息可以用于指示试探性关联的生命周期，当Non-AP MLD与AP MLD之间没有交互的时间超过该生命周期时，AP MLD删除之前与该Non-AP MLD协商的信息。
可选的，试探性关联控制字段和试探性关联生命周期可以携带于一个新定义的元素中。参见图6b，图6b是本申请实施例提供的另一个新元素的帧结构示意图。如图6b所示，该元素的帧结构包括元素标识、长度、试探性关联控制字段以及试探性关联生命期。其中，试探性关联控制字段中包括1比特的Non-AP MLD触发802.1X认证指示位、1比特的Non-AP MLD触发四步握手指示位、以及1比特的Non-AP MLD触发STA-AP映射通知指示位，其余4比特预留。
可选的，Non-AP MLD可以接收每个AP MLD发送的试探性关联的能力指示信息。该试探性关联的能力指示信息可以用于指示该AP MLD是否支持试探性关联。该试探性关联的能力指示信息可以携带于快速BSS转移元素(Fast BSS Transition element)、多链路聚合(MLA)元素或移动域元素(Mobility Domain element)中。其中，该快速BSS转移元素可以携带于信标(Beacon)帧中。
具体地，可以在邻居汇报元素(neighbor report element)和精简的邻居汇报元素(reduced neighbor report element)中增加1bit来指示邻居AP或者邻居AP MLD是否支持试探性关联。邻居汇报元素可以描述一个邻居AP及该邻居AP上的BSS信息。AP可以通过携带多个邻居汇报元素来指示所有邻居的相关信息。其中，利用邻居汇报元素中BSSID information字段中的保留比特来指示该BSS是否支持试探性关联。利用精简的邻居汇报元素中BSS Parameter字段中的保留比特来指示该BSS是否支持试探性关联。
参见图7a，图7a是本申请实施例提供邻居汇报元素的一种帧结构示意图。如图7a所示，邻居汇报元素包括元素标识符、长度、BSS标识符、BSSID信息、操作类别、信道编号、物理层类型以及可选的子元素等。BSSID字段，用于指示上报的邻居AP对应的BSSID；BSSID信息字段，用于指示上报的BSSID的相关信息；Operating Class(操作类别)字段和channel Number(信道编号)字段，用于指示上报的BSSID在哪一个信道上；PHY Type(物理层类型)字段，用于指示上报的BSSID对应AP的物理层类型；Optional subelements(可选的子元素)字段：承载一些可选的子元素。
其中，对于BSSID信息字段，其携带以下具体信息：1、AP Reachability字段：指示该AP是否可达。2、Security字段：指示该上报的AP是否支持与现有连接相同的安全配置。3、Key Scope字段：指示该上报的AP与发送该Report的AP是否是相同的认证者。4、Capabilities字段：指示该上报的AP一些可选的能力信息。5、Mobility domain字段：指示该上报的AP与发送该Report的AP是否在同一个移动域中。6、High Throughput字段：指示该上报的AP的HT capabilities element(携带optional subelement字段中)与发送该Report的AP的HT capabilities element内容相同。7、Very High Throughput字段：指示该上报的AP的VHT capabilities element与发送该Report的AP的VHT capabilities element内容相同。8、FTM(fine timing measurement)字段：指示该上报的AP是否支持精细定时测量。9、High Efficiency字段：指示该上报的AP的HE capabilities element与发送该Report的AP的HE capabilities element内容相同。10、ER(Extended range)BSS字段：指示该上报的AP发送的Beacon采用HE ER SU PPDU方式发送。11、Collocated AP字段：指示该上报 的AP与发送该Report的AP是否是共位置AP。12、Unsolicited Probe Response Active字段：指示该上报的AP是否开启主动探测响应。13、Member of ESS with 2.4/5GHz co-located AP字段：指示该上报的AP是否与一个2.4/5GHz AP共位置且是一个扩展服务集的成员。14、OCT supported with reporting AP字段:指示该上报的AP是否支持通过OCT(On-channel tunneling，随路隧道)机制来交换管理帧类型的MPDU。15、Co-located with 6GHz AP字段：指示该上报的AP是否与一个6GHZ AP共位置。16、预留字段。
对于Capabilities字段，其具体还有以下信息字段：Spectrum management字段：指示该上报的AP是否支持频谱管理功能；QoS(服务质量，quality of service)字段：指示该上报的AP是否支持QoS机制；APSD(automatic power save delivery)字段：指示该上报的AP是否支持自动节能传输机制；Radio Measurement字段：指示该上报的AP是否支持无线测量功能。
可选的，AP MLD可以通过在管理帧，比如信标帧，探测响应帧中携带精简邻居汇报元素。Non-AP MLD在扫描时，接收AP MLD发送的关联帧，从而获得周围的邻居AP信息，然后选择合适的AP MLD进行关联。
参见图7b，图7b是本申请实施例提供精简的邻居汇报元素的一种帧结构示意图。如图7b所示，精简的邻居汇报元素包括元素标识符、长度、一个或多个邻居AP信息字段。一个邻居AP信息字段中包括目标信标传输时间(target beacon transmission time，TBTT)信息字段头、操作类别、信道号以及TBTT信息集合。TBTT信息集合中包括一个或多个TBTT信息字段。
其中，对于TBTT信息字段头，其携带以下信息：TBTT info Field Type字段，用于指示TBTT info的类型，其与TBTT信息长度字段一起指示TBTT info字段的格式；Filtered neighbor AP字段，用于指示该Neighbor AP info字段中所携带的所有BSS的SSID是否与Probe Request帧中的SSID相匹配；Reserved字段(1bit)；TBTT info count字段，用于指示TBTT信息集中含有TBTT信息字段的个数；TBTT info Length字段，用于指示每个TBTT info field的长度。
TBTT info Length字段的不同长度所携带的具体信息格式如下述表1所示。
Figure PCTCN2021095343-appb-000001
Figure PCTCN2021095343-appb-000002
参见图7c，图7c是本申请实施例提供的12字节的TBTT信息长度字段的一种帧结构示意图。如图7c所示，12字节的TBTT信息长度字段包括邻居AP的TBTT偏置、BSS标识符、短服务集标识以及BSS参数。Neighbor AP TBTT offset字段：指示该上报的BSS与发送该Report的BSS的Beacon发送时间的偏置。BSSID字段：指示该上报的BSS所对应的BSS标识符。Short SSID字段：指示该BSS所属的服务集标识符。BSS Parameter(BSS参数)字段：指示该BSS的相关参数。
其中，BSS Parameter字段具体包含以下指示信息：(1)OCT recommended(推荐使用随信道隧道机制)字段：指示该上报的BSS期望通过OCT机制与其交换管理类型的MPDU。(2)Same SSID(相同服务集标识)字段：指示该上报的AP和传输该Report的AP是否具有相同的SSID。(3)Multiple BSSID(多基本服务集标识)字段：指示该上报的AP是不是属于某个multiple BSSID集合的一部分。(4)Transmitted BSSID(发送基本服务集标识)字段：如果该上报的AP是属于某个multiple BSSID集合的一部分，则进一步指示该上报的AP是Transmitted BSSID还是non-transmitted BSSID。(5)Member Of ESS With 2.4/5GHz Co-Located AP(与2.4/5GHz AP共位置且为扩展服务集成员)字段：指示该上报的AP是否与一个2.4/5GHz AP共位置(即是不是6GHz only的AP)且是一个扩展服务集的成员。(6)Unsolicited Probe Response Active(主动探测响应活跃)字段：指示该上报的AP是否开启主动探测响应。(7)Co-located AP(共位置AP)字段：指示该上报的AP与传输该Report的AP是否是共位置的。(8)预留字段。
S103，Non-AP MLD与一个或多个第二AP MLD进行802.1X认证和四步握手派生PTK和GTK过程。
具体地，在上述多链路关联响应帧指示关联成功后，Non-AP MLD与AP MLD进行802.1X认证来获得PMK，并通过四步握手可派生得到成对临时秘钥(pairwise transient key，PTK)以及组播临时秘钥(group temporal key，GTK)。参见图8，图8是本申请实施例提供的Non-AP MLD与一个AP MLD进行802.1X认证和四步握手派生PTK和GTK的交互示意图。如图8所示，AP MLD向Non-AP MLD发送扩展认证协议(extensible authentication protocol，EAP)请求(request)/身份证明(identity)；Non-AP MLD向AP MLD返回EAP响应/身份证明；AP MLD向认证服务器(authtication server，AS)发送Radius接入请求，等等一系列交互，在EAP成功之后进行四步握手派生PTK和GTK过程。如图8所示，四步握手派生PTK和GTK过程包括：Non-AP MLD向AP MLD发送秘钥消息1(Key Message1)；AP MLD向Non-AP MLD返回秘钥消息2(Key Message2)；Non-AP MLD向AP MLD发送秘钥消息3(Key Message3)；AP MLD向Non-AP MLD返回秘钥消息4(Key Message4)。获得PTK和GTK之后，Non-AP MLD和AP MLD根据发送的数据报文的类型采用对应的秘钥进行加密。
可理解的，Non-AP MLD与多个第二AP MLD进行802.1X认证和四步握手派生PTK和GTK过程，可以参考单个Non-AP MLD与单个AP MLD进行802.1X认证和四步握手派 生PTK和GTK过程，在此不再赘述。还可理解的，Non-AP MLD可以同时与多个第二AP MLD进行802.1X认证和四步握手派生PTK和GTK过程，以提高漫游的成功率。这是因为Non-AP MLD中的一个第一STA可以与一个第二AP MLD进行802.1X认证和四步握手派生PTK和GTK过程，所以Non-AP MLD中的多个第一STA可以同时与多个第二AP MLD进行802.1X认证和四步握手派生PTK和GTK过程。
S104，Non-AP MLD从一个或多个第二AP MLD中确定出最终的目标AP MLD。
S105，Non-AP MLD向目标AP MLD发送一个指示信息用于触发目标AP MLD更新分布式系统(distribution system，DS)中的站点与接入点之间的映射关系。
具体地，上述指示信息可以携带于A-控制(A-Control)字段中。可选的，该指示信息也可以携带于一个新定义的帧中，为便于描述，下文将携带该指示信息的帧称为STA-AP Mapping Notify帧。可理解的，携带该指示信息的帧也可以称为STA-AP Mapping触发帧等等，本申请实施例对携带该指示信息的帧的名称不做限定。
可选的，Non-AP MLD可以根据该Non-AP MLD与多个第二AP MLD之间的关联是否成功、各个第二AP MLD的能力以及该Non-AP MLD与各个第二AP MLD的链路质量，从该多个第二AP MLD中选择出一个最终的目标AP MLD。可理解的，在只有一个第二AP MLD的情况下，Non-AP MLD直接向该第二AP MLD发送指示信息。
在一个可选实施例中，上述步骤S101-步骤S103，可以描述为：Non-AP MLD利用某条或者某几条Disable的link与一个或者多个第二AP MLD同时进行Multi-link Tentative Association(多链路试探性关联)，进行各种操作/流程，除了触发DS-STA-Notify.request原语的发送。
在另一个可选实施例中，假设Non-AP MLD存在3条link，Non-AP MLD可以将其中与第一AP MLD的两条链路的状态设置为disable，然后利用相应的STA同时与邻近两个第二AP MLD进行Tentative Reassociation。Non-AP MLD根据关联是否成功、该邻近两个第二AP MLD的能力以及Non-AP MLD与各个第二AP MLD的链路质量，决定最终与哪个第二AP MLD进行重关联，然后Non-AP MLD可以跳过802.1X认证，直接进行PTK和/或GTK派生。
可选的，由于Non-AP MLD可以跳过802.1X认证，所以Non-AP MLD需要发送一个新定义的帧，来触发与新AP MLD的四步握手派生PTK和GTK。
可理解的，在实际应用中，本申请实施例提供的多链路试关联方法的流程可以多于上述步骤101-步骤S104。下面将对本申请实施例提供的多链路试关联方法可能还包括的流程进行说明。
一个示例中，在步骤S101之前，还包括步骤S106：Non-AP MLD向第一AP MLD发送链路状态指示信息，该链路状态指示信息用于指示Non-AP MLD与第一AP MLD之间的链路状态为Disable的链路。其中，该链路状态指示信息可以包括Non-AP MLD与第一AP MLD之间的一条或多条链路标识和每条链路标识对应的状态。可选的，该链路状态指示信息还可以指示Non-AP MLD与第一AP MLD之间的一条或多条链路的状态为Disable的原因。可理解的，Non-AP MLD与第一AP MLD之间的链路状态为Disable的原因可以包括节能、低接收信号强度指示和试探性关联中的一种。还可理解的，本申请实施例中链路状 态指示信息指示的Non-AP MLD与第一AP MLD之间的一条或多条链路的状态为Disable的原因是试探性关联。
本申请实施例通过链路状态指示信息来告知第一AP MLD某条或某几条链路因为试探性关联而Disable，避免第一AP MLD因为待传输的数据量大，而尝试请求该某条或该某几条链路开启。
一个示例中，在上述步骤S105之前，还包括步骤S107：Non-AP MLD向第一AP MLD发送第一请求，该第一请求用于请求该第一AP MLD反馈该第一AP MLD的邻居信息。这里的邻居信息可以指第一AP MLD周围的其他AP MLD，或者第一AP MLD所在的BSS周围的其他BSS。具体地，Non-AP MLD可以向第一AP MLD发送BSS转移管理询问(BSS Transition Management Query)帧，该BSS转移管理询问帧用于请求该第一AP MLD反馈该第一AP MLD周围的邻居信息。第一AP MLD向Non-AP MLD发送BSS转移管理请求(BSS Transition Management Request)帧。Non-AP MLD接收到该BSS转移管理请求帧之后，向第一AP MLD返回BSS转移管理响应(BSS Transition Management Response)帧。
可选的，上述BSS转移管理询问帧中可以包括BSS转移询问原因字段和BSS转移候选列表字段。BSS转移询问原因字段可以用于指示进行BSS转移管理询问的原因；BSS转移候选列表字段可以携带一个或者多个邻居报告信息元素(Neighbor Report element)。参见图9a，图9a是本申请实施例提供的BSS转移管理询问帧的部分或全部帧结构的示意图。
上述BSS转移管理请求帧中可以包括以下字段：包含倾向的候选者列表(Perferred Candidate list included)指示位(Bit 0)、简略(Abridged)指示位(Bit 1)、立即去关联(Disassociation Imminent)指示位(Bit 2)、BSS终止(BSS Termination Included)指示位(Bit 3)、ESS立即去关联(ESS Disassociation Imminent)指示位(Bit 4)、去关联计时器(Disassociation Timer)字段以及有效期(Validity Interval)字段等等。
参见图9b，图9b是本申请实施例提供的BSS转移管理请求帧的部分或全部帧结构的示意图。其中，当Perferred Candidate list included指示位置0，表示Non-AP MLD可以忽略BSS转移候选者列表(BSS Transition Candidate List)字段里的信息；当Perferred Candidate list included指示位置1，表示AP MLD希望Non-AP MLD能处理BSS Transition Candidate List字段里的信息。Disassociation Imminent指示位用于指示Non-AP MLD是否会被去关联。当Disassociation Imminent指示位置1时，表示该Non-AP MLD会被AP MLD立即去关联；当Disassociation Imminent指示位置0时，表示去关联不会立即发生。当BSS Termination Included指示位置1时，表示该BSS会被终止；当BSS Termination Included指示位置0时，表示不会携带BSS终止持续时间(BSS Termination Duration)字段。ESS Disassociation Imminent指示位用于指示是否携带会话信息通用资源定位符(Session Information URL)字段以及该Non-AP MLD会被ESS去关联。当ESS Disassociation Imminent指示位置1，表示该STA会被ESS去关联，并且Session Information URL字段会出现；当ESS Disassociation Imminent指示位置0时，表示该STA不会立即被ESS去关联。Disassociation Timer字段用于指示AP MLD会在多久后发送去关联帧给该Non-AP MLD。Validity Interval字段用于指示BSS transition candidate list信息的有效期。
上述BSS转移管理响应帧中可以包括BSS转移管理状态码(BTM Status Code)字段、 BSS终止延时(BSS Termination Delay)字段、目标BSS标识(Target BSSID)以及BSS转移候选者列表字段等等。参见图9c，图9c是本申请实施例提供的BSS转移管理响应帧的部分或全部帧结构的示意图。其中，BTM Status Code字段用于指示对于BSS切换请求反馈的状态信息，比如指示是否接受BSS切换。BSS Termination Delay字段用于指示Non-AP MLD希望AP MLD多久后才终止该BSS。Target BSSID用于指示切换的目标BSS的标识。BSS Transition Candidate List字段可以携带一个或者多个邻居报告信息元素。
可选的，本申请实施例的BSS转移管理响应帧中的目标BSS标识可以携带目标AP MLD的服务接入点(service access point，SAP)MAC Address。
可选的，步骤S107也可以为：Non-AP MLD主动向第一AP MLD发送BSS转移管理询问帧，请求第一AP MLD提供其邻居信息。可选的，步骤S107还可以为：Non-AP MLD跳转到其他信道(这里的其他信道可以指与该第一AP MLD的信道不同的信道)上进行主动或者被动扫描来获得该第一AP MLD的邻居信息。
一个示例中，在步骤S104之后，还包括步骤S108：目标AP MLD向分布式系统发送DS-STA-Notify.request原语。该DS-STA-Notify.request原语中携带目标AP MLD与Non-AP MLD之间的mapping信息，或者目标AP MLD与Non-AP MLD之间的关联关系。该DS-STA-Notify.request原语用于告知分布式系统的STA-AP Mapping信息。这是因为每个Non-AP MLD只能关联一个AP MLD，分布式系统必须知道哪个AP MLD服务该Non-AP MLD，然后将目的地址为该Non-AP MLD的MAC地址的数据包递交给相应的AP MLD。
可选的，在目标AP MLD发送DS-STA-Notify.request原语之前，Non-AP MLD可以与目标AP MLD进行块确认(block acknowledgement，BA)协商。
可选的，上述DS-STA-Notify.request原语可以携带Non-AP MLD的SAP MAC地址和更新类型(Update Type)。该更新类型可以包括ADD(增加)、MOVE(移动)和DELETE(删除)三种类型。ADD用于Non-AP MLD初次与某个AP MLD关联时，AP MLD发送的DS-STA-Notify.request原语中。DELETE用于Non-AP MLD初次与某个AP MLD去关联时，AP MLD发送的DS-STA-Notify.request原语中。MOVE用于Non-AP MLD从某个AP MLD切换到一个新的AP MLD时，AP MLD发送的DS-STA-Notify.request原语中。
由此可知，本申请实施例中目标AP MLD发送DS-STA-Notify.request原语携带的更新类型为MOVE。当客户端为Non-AP MLD时，目标AP MLD发送的DS-STA-Notify.request原语中的MAC Address为该Non-AP MLD的SAP MAC Address。可选的，上述STA-AP Mapping信息中也使用Non-AP MLD和AP MLD的SAP MAC Address。
一个示例中，在步骤S104之后，还包括步骤S109：如果信道空闲状态下第一AP MLD与Non-AP MLD之间没有数据传输的时间超过某一预定时间，则Non-AP MLD可以主动向第一AP MLD发送多链路去关联帧。然后，Non-AP MLD可以将与第一AP MLD之间的剩余链路的状态为enable的一个或多个第二STA切换到目标AP MLD对应链路的信道上，并通知目标AP MLD该一个或多个第二STA与该目标AP MLD之间的链路状态变为Enable状态。
可选的，还可以在步骤S104之后，Non-AP MLD立即向第一AP MLD发送多链路去关联帧，并切换到目标AP MLD对应链路的信道上，并通知目标AP MLD该链路的状态变 为Enable状态。
可理解的，上述步骤S108与上述步骤S109可以同时执行，步骤S108也可以在步骤S109之前执行，步骤S108还可以在步骤S109之后执行，本申请实施例对步骤S108和步骤S109之间的执行顺序不做限定。
本申请实施例中，Non-AP MLD断开与当前关联的AP MLD(即第一AP MLD)之间的部分链路，然后利用链路状态为断开的STA向一个或多个第二AP MLD发送多链路关联请求帧，请求与该一个或多个第二AP MLD进行多链路试探性关联；一个或多个第二AP MLD向Non-AP MLD返回多链路关联响应帧；如果该多链路关联响应帧指示同意进行多链路试探性关联，则Non-AP MLD可以与一个或多个第二AP MLD进行802.1X认证和四步握手交换秘钥过程；在四步握手交换秘钥完成之后，Non-AP MLD根据关联是否成功、各个第二AP MLD的能力以及Non-AP MLD与各个第二AP MLD的链路质量，从一个或多个第二AP MLD中选择一个目标AP MLD，并通过一个指示信息触发目标AP MLD更新分布式系统中的站点与接入点之间的映射关系。可以实现多链路设备在进行漫游时，减少数据传输的中断时间，理想情况下可以使漫游过程中的不存在数据传输中断，即在任意时刻，始终有可用的链路进行数据传输。
为更好地理解本申请实施例一的技术方案，下面结合两个具体示例对实施例一的技术方案进行示例性说明。其中，示例1示出了实施例一提供的多链路试关联方法的一种具体流程；示例2示出了实施例一提供的多链路试关联方法的一种信令交互流程。
可理解的，下文的具体示例，均假设第一AP多链路设备为AP MLD1，第二AP多链路设备为AP MLD2；AP MLD1中包括AP11和AP12，AP MLD2中包括AP21和AP22；Non-AP多链路设备中包括STA1和STA2。Non-AP多链路设备在发生漫游之前，与AP MLD1关联。
示例1：参见图10，图10是本申请实施例提供的Non-AP MLD在漫游过程中切换AP MLD的一示意图。如图10所示，STA2@Non-AP MLD表示Non-AP MLD的STA 2；CH表示channel(信道)；CH1@Band 1表示频段1上的信道1。Non-AP MLD在漫游过程中切换AP MLD的过程包括但不限于以下步骤：
步骤1：Non-AP MLD向AP MLD1发送链路状态指示信息。该链路状态指示信息用于指示链路12(link 12)的状态为断开(或Disable)。
其中，该链路状态指示信息中可以携带link 12所对应的链路标识(link ID)，该告知信息还可以指示link 12的状态为Disable。
可选的，该链路状态指示信息中还可以携带原因码(Reason Code)字段来指示link 12的状态为Disable的原因。可理解的，链路的状态为断开(或Disable)的原因可以为节能(power save)，或者低接收信号强度指示(Low received signal strength indication，Low RSSI)，或者试探性关联(tentative association)等等。还可理解的，本申请实施例中链路状态指示信息携带的原因码(Reason Code)字段可以设置为试探性关联(tentative association)。
可选的，该链路状态指示信息可以通过链路11(link 11)发送，也可以通过link 12发送，本申请实施例对此不做限定。可理解的，该链路状态指示信息无论通过哪条链路发送， 其携带的信息不发生改变。
步骤2：Non-AP MLD的STA2(即STA2@Non-AP MLD)跳转到频段4的信道2(即CH2@Band 4)上，发起与AP MLD2的多链路试探性关联。
具体地，STA2@Non-AP MLD切换到链路22(link 22)上开始进行BSS转移，首先与AP MLD2进行802.11开放认证流程，然后再发送多链路重关联请求(multi-link reassociation request)帧，该多链路重关联请求帧可以携带试探性关联指示信息，该试探性重关联指示信息可以用于指示此次重关联操作的类型是否为试探性关联，或者指示该多链路重关联请求帧请求进行的关联操作的类型是否为试探性关联。其中，该试探性关联指示信息可以携带于该多链路重关联请求帧的多链路聚合(multi-link aggregation，MLA)元素(MLA element)的公共信息(common information)字段中。
可选的，该多链路重关联请求帧还可以指示链路21(link 21)的状态为Disable。这是因为Non-AP MLD的STA 1(即STA1@Non-AP MLD)与AP MLD1还未断开连接，即STA1与AP11之间的链路11的状态为enable。进一步可选的，该多链路重关联请求帧还可以通过携带Reason Code字段来指示link 21的状态为Disable的原因。这里的Reason Code字段可以设置为“与旧AP MLD关联(Association with old AP MLD)”。
可选的，Non-AP MLD在与AP MLD2进行重关联或多链路试探性重关联时，可以使用Non-AP MLD的一个新SAP MAC Address。具体地，Non-AP MLD在多链路重关联请求帧中同时携带Non-AP MLD的新SAP MAC Address和旧SAP MAC Address。Non-AP MLD的旧SAP MAC Address可以用于AP MLD2去AP MLD1取回未传完的数据包。
可理解的，Non-AP MLD的旧SAP MAC Address可以指Non-AP MLD与AP MLD1关联时所使用的SAP MAC Address。
可理解的，由于Non-AP MLD采用新SAP MAC Address与AP MLD2进行多链路试探性重关联，所以Non-AP MLD需要重新进行802.1X认证。
步骤3：AP MLD2在链路22上向Non-AP MLD的STA 2返回多链路重关联响应(lulti-link association response)帧。
其中，如果多链路重关联响应帧指示Non-AP MLD与AP MLD2关联成功，则Non-AP MLD可以与AP MLD 2进行诸如BA Agreement建立等协商交互操作，并且AP MLD 2不能发送DS-STA-Notify.request原语来通知分布式系统更新STA-AP Mapping信息。
步骤4：Non-AP MLD在某一时刻向AP MLD 2发送STA-AP Mapping Notify帧，以触发AP MLD 2发送DS-STA-Notify.request原语通知DS更新STA-AP Mapping信息。
其中，Non-AP MLD在何时发送STA-AP Mapping Notify帧，可以综合各种因素来决定。比如，在Non-AP MLD与AP MLD2的关联优于Non-AP MLD与AP MLD1的关联时发送STA-AP Mapping Notify帧。
步骤5：AP MLD2向Non-AP MLD返回确认帧，并发送DS-STA-Notify.request原语通知DS更新STA-AP Mapping信息。
其中，本申请实施例中DS-STA-Notify.request原语携带Non-AP MLD的服务接入点(service access point，SAP)MAC地址，DS-STA-Notify.request原语携带的更新类型为MOVE。
可选的，AP MLD2发送DS-STA-Notify.request原语通知DS更新STA-AP Mapping信息之后，可以到AP MLD1处获取传输给Non-AP MLD的未传完数据。
步骤6：Non-AP MLD的STA1(即STA1@Non-AP MLD)向AP MLD1发送多链路去关联(multi-link disassociation)帧，然后跳转到频段3的信道1(即CH1@Band 3)上与AP MLD2的AP21(即AP 21@AP MLD 2)进行数据交换。
具体地，Non-AP MLD通知AP MLD2链路21(link 21)的状态变为enable的方式包括两种，分别为隐式通知和显式通知。其中，隐式通知为：如果Non-AP MLD有上行数据需要传输，Non-AP MLD可以在链路21(link 21)上直接发送上行数据，通过link 21上的上行数据隐式通知AP MLD2，link 21的状态已经变为enable。显式通知为：如果Non-AP MLD没有上行数据需要传输，Non-AP MLD可以向AP MLD2发送一个QoS Null帧来通知AP MLD 2该link 21的状态已经变为enable。或者通过在link22上发送的数据帧的A-Control字段中携带link21的链路标识和状态信息来通知AP MLD2。
可选的，Non-AP MLD的STA1可以设定一个时间值。如果信道空闲状态下AP MLD1与Non-AP MLD之间没有数据传输的时间超过该时间值，则Non-AP MLD的STA1可以主动发送多链路去关联帧给AP MLD1。
可选的，Non-AP MLD与AP MLD1在关联时就携带一个时间值。如果信道空闲状态下AP MLD1与Non-AP MLD之间没有数据传输的时间超过该时间值，则Non-AP MLD可以自动断开链路，不需要Non-AP MLD发送多链路去关联帧给AP MLD1。
可选的，当Non-AP MLD收到AP MLD2针对秘钥消息4返回的确认帧(ACK帧)时，Non-AP MLD的STA1可以发送多链路去关联帧给AP MLD1。
可理解的，在实际应用中，Non-AP MLD在漫游过程中切换AP MLD的过程可以少于图10所示的步骤，也可以多于图10所示步骤，本申请实施例对此不做限定。
本申请实施例中，Non-AP MLD断开与当前关联的AP MLD(即AP MLD1)的一条或者部分链路；然后用链路状态为断开状态的STA与新的目标AP MLD(即AP MLD2)进行多链路关联；在四步握手派生PTK和GTK完成后，目标AP MLD(即AP MLD2)才发送DS-STA-Notify.request原语通知DS更新STA-AP Mapping信息，并到之前关联的AP MLD(即AP MLD1)处取回传输给Non-AP MLD的未传完数据。可以减少数据传输的中断时间，理想情况下不存在数据传输中断，即在任意时刻，始终有可用的链路进行数据传输。
示例2：参见图11，图11是本申请实施例提供的Non-AP MLD在漫游过程中切换AP MLD的信令交互示意图。图11中Non-AP MLD在漫游过程中切换AP MLD的过程可以不包括前述图10中的步骤4，即Non-AP MLD的STA2无需向AP MLD 2发送STA-AP Mapping Notify帧来触发AP MLD 2发送DS-STA-Notify.request原语。本申请实施例通过约束AP MLD2在收到Key Message 4后，直接发送DS-STA-Notify.request原语给DS，以此实现DS更新STA-AP Mapping信息。
可选的，Non-AP MLD可以在收到AP MLD2针对Key Message 4返回的ACK帧后，立即发送多链路去关联帧给AP MLD1，然后切换到AP MLD2对应的链路信道上，并通知AP MLD2该链路状态变为enable状态。可选的，Non-AP MLD还可以在收到AP MLD2针 对Key Message 4返回的ACK帧后，如果信道空闲状态下AP MLD1与Non-AP MLD之间没有数据传输的时间超过某个值，则Non-AP MLD主动发送多链路去关联帧给AP MLD1，然后切换到AP MLD2对应的链路信道上，并通知AP MLD2该链路的状态变为enable状态。
可理解的，从图11所示的信令交互过程可以看出，Non-AP MLD在整个漫游过程中的数据传输没有中断，即Non-AP MLD在任意时刻，始终有可用的链路可以进行数据传输。
由于本申请实施例一在多链路设备的关联/重关联过程中引入Tentative Association来实现数据传输的不中断，所以在不同的状态下，Non-AP MLD与AP MLD之间允许传输的帧类型也需要重新定义。
参见图12a，图12a是本申请实施例提供的不同状态间的转换关系和不同状态下所允许发送的帧类型的一示意图。如图12a所示，状态(State)5是本申请实施例新增的一种状态。在State 5下，允许传输的帧(或者允许提供的数据服务)包括帧类别1、帧类别2、帧类别3以及帧类别4中的数据帧、控制帧或管理帧。其中，帧类别1和帧类别2下的各种帧与现有协议相同。帧类别3中的数据帧可以指：在基础BSS和网格BSS中，站点间以太网类型不等于0X0800或者0X86dd的数据帧(Data frames between STAs with Ethernet_Type not equeal to 0X0800 or 0X86dd in an infrastructure BSS or in an MBSS)。帧类别4可以指以太网类型为0X0800的数据帧(Data frame with Ethernet_Type＝0x0800或0X86dd)。另外一种帧类别3和帧类别4的定义方式如下：帧类别3可以指MAC帧头中的Address 3为当前关联的AP的BSSID；帧类别4可以指MAC帧头中的Address 3为非当前关联的AP的BSSID的MAC地址。可理解的，在AP MLD没发送DS-STA-Notify.request原语之前，本申请实施例只允许传输帧类别1、2以及3中的各种帧。在AP MLD发送DS-STA-Notify.request原语或者Non-AP MLD发送STA-AP Mapping Notify帧后，本申请实施例才允许传输任何帧，如帧类别1、2、3以及4中的各种帧。换言之，只有AP MLD发送DS-STA-Notify.request原语之后，才允许Non-AP MLD与DS直接通信，而在之前，只允许通过AP MLD以代理的方式与DS通信。
参见图12b，图12b是本申请实施例提供的不同状态间的转换关系和不同状态下所允许发送的帧类型的另一示意图。如图12b所示，本申请实施例不新增状态。在状态4下，允许传输帧类别1、帧类别2、帧类别3以及帧类别4中的数据帧、控制帧或管理帧。由图12b可知，状态3变为状态4的过程中，STA MLD和AP MLD已经成功进行四步握手派生PTK和GTK并且触发了AP MLD发送DS-STA-Notify.request原语，所以本申请实施例通过改变状态3变为状态4的条件，来适应本申请实施例一的多链路试关联方法。
实施例二
本申请实施例还提供一种多链路设备的初始关联方法，该初始关联方法利用Non-AP MLD的多个Radio同时与多个AP MLD(或者AP)发起试探性关联，再根据关联情况，选择最优的AP MLD(或者AP)进行关联，可以提高Non-AP MLD在初始关联过程中的关联成功率，提高关联速度。
可理解的，本申请实施例二可以单独应用于Non-AP MLD与AP MLD的初始关联场景 中，也可以结合实施例一共同应用，本申请实施例对此不做限定。
下面将从Non-AP MLD与AP MLD交互的角度，对本申请实施例提供的初始关联方法进行说明。
一个示例中，参见图13a，图13a是本申请实施例提供的初始关联过程中Non-AP MLD与AP MLD的一交互示意图。如图13a所示，以3个AP MLD和1个Non-AP MLD为例，对本申请实施例提供的初始关联方法进行说明。具体地，该初始关联方法包括：(1)Non-AP MLD在一条链路(如图13a中的链路1)上向一个AP MLD(如图13a的AP MLD1)发起关联，并指示与AP MLD 1的其他链路为Disable状态，紧接着进行802.1X认证获得PMK；(2)Non-AP MLD利用剩余的多条链路(如图13a的链路2和链路3)在不同信道上发送多链路重关联请求(Multi-link Re-association Request)帧，来发起与其他多个AP MLD(如图13a的AP MLD2和AP MLD3)的试探性关联，并且在关联请求帧中指示其他链路为Disable状态；(3)Non-AP MLD根据关联是否成功、各个AP MLD(如图13a的AP MLD1、AP MLD2、AP MLD3)的能力以及Non-AP MLD与各个AP MLD的链路质量，确定目标AP MLD，即确定最终与哪个AP MLD进行关联，然后进行秘钥(即PTK和/或GTK)派生。
可选的，Non-AP MLD可通过发送一个新定义的帧，来触发与目标AP MLD的四步握手派生PTK和GTK。
可理解的，图13a所示的Non-AP MLD与AP MLD的交互过程中，Non-AP MLD只需进行一次802.1X认证，无需与多个AP MLD进行多次802.1X认证，可以减少Non-AP MLD在初始关联过程中的关联时延，提高关联速度。
另一个示例中，参见图13b，图13b是本申请实施例提供的初始关联过程中Non-AP MLD与AP MLD的另一交互示意图。如图13b所示，以3个AP MLD和1个Non-AP MLD为例，对本申请实施例提供的初始关联方法进行说明。具体地，该初始关联方法包括：(a)Non-AP MLD在多条链路(如图13b的链路1、链路2以及链路3)上发送多链路关联请求(Multi-link Association Request)帧，同时与多个AP MLD(如图13b的AP MLD1、AP MLD2以及AP MLD3)发起试探性关联，并在关联请求帧中指示其他链路为Disable状态；(b)Non-AP MLD根据关联是否成功、各个AP MLD的能力以及Non-AP MLD与各个AP MLD的链路质量，确定目标AP MLD，即确定最终与哪个AP MLD进行关联；(c)Non-AP MLD通过发送EAP-Start来触发与目标AP MLD进行802.1X认证、四步握手派生PTK和GTK等流程。
可理解的，由于EAP-Start是可选的，所以在这种方式下，目标AP MLD不能主动发起802.1X认证。
可理解的，图13b所示的Non-AP MLD与AP MLD的交互过程中，Non-AP MLD直接同时与多个AP MLD发起试探性关联，在接收到多链路关联响应帧之后，从该多个AP MLD中选择一个AP MLD进行802.1X认证、四步握手派生PTK和GTK等流程。可以提高Non-AP MLD在初始关联过程中的关联成功率，通过并行(同时)发起试探性关联提高关联速度。
又一个示例中，参见图13c，图13c是本申请实施例提供的初始关联过程中Non-AP MLD与AP MLD的又一交互示意图。如图13c所示，以3个AP MLD和1个Non-AP MLD为例， 对本申请实施例提供的初始关联方法进行说明。具体地，该初始关联方法包括：(A)Non-AP MLD在多条链路(如图13c的链路1、链路2以及链路3)上发送多链路关联请求帧，同时与多个AP MLD(如图13c的AP MLD1、AP MLD2以及AP MLD3)发起试探性关联，并在关联请求帧中指示其他链路为Disable状态，然后与每个AP MLD都进行802.1X认证，四步握手派生PTK和GTK等流程；(B)Non-AP MLD根据关联是否成功、各个AP MLD的能力以及Non-AP MLD与各个AP MLD的链路质量，确定目标AP MLD，即确定最终与哪个AP MLD进行关联；(C)Non-AP MLD通过发送STA-AP Mapping Notify帧，来触发目标AP MLD发送DS-STA-Notify.request原语来通知分布式系统相应的STA-AP mapping信息。
可理解的，图13c所示的Non-AP MLD与AP MLD的交互过程中，Non-AP MLD直接同时与多个AP MLD发起试探性关联，并与每个AP MLD进行802.1X认证，四步握手派生PTK和GTK等流程，最后从该多个AP MLD中选择一个AP MLD，向其发送STA-AP Mapping Notify帧，来触发目标AP MLD发送DS-STA-Notify.request原语，可以提高Non-AP MLD在初始关联过程中的关联成功率。
实施例三
本申请实施例还提供一种应用于Non-AP MLD漫游场景下非共址(non-collocated)多链路设备的关联方法。下面将结合Non-AP MLD的最优关联场景对本申请实施例提供的非共址多链路设备的关联方法进行说明。为便于描述，下面假设Non-AP MLD包括两个STA，分别为STA1和STA2，AP MLD包括两个AP，分别为AP1和AP2；AP MLD的一条链路或者AP可以工作在2.4GHz频段，另一条链路或者AP可以工作在5GHz频段。可理解的，在实际应用中，Non-AP MLD包括的STA数量可能多于两个，AP MLD包括的AP数量也可能多于两个，在Non-AP MLD包括的STA数量多于两个和AP MLD包括的AP数量多于两个的情况下，可以参考本申请实施例中对两个STA和两个AP的描述，在此不再赘述。
参见图14，图14是本申请实施例提供的Non-AP MLD移动过程中的最优关联场景示意图。如图14所示，当Non-AP MLD停留在区域1时，Non-AP MLD的两个STA与AP MLD1的两个AP进行关联。当Non-AP MLD从区域1移动到区域2，并停留在区域2时，Non-AP MLD的两个STA可以分别与AP MLD1和AP MLD2中工作在2.4GHz频段上的AP进行关联,并建立一个Non-Collocated MLD3，Non-Collocated MLD3包括AP MLD1和AP MLD2中工作在2.4GHz频段上的AP。当Non-AP MLD从区域2移动到区域3，并停留在区域3时，Non-AP MLD的两个STA与AP MLD2的两个AP进行关联。
在上述图14所示的最优关联场景下，进一步参见图15，图15是本申请实施例提供的非共址多链路设备的关联方法的一示意流程图。如图15所示，该非共址多链路设备的关联方法包括但不限于以下步骤：
S201，Non-AP MLD向AP MLD2发送多链路关联请求帧。
S202，AP MLD2向AP MLD1发送多链路建立请求(MLD Setup Request)。
S203，AP MLD1向AP MLD2返回多链路建立响应(MLD Setup Response)。
S204，AP MLD2向Non-AP MLD返回多链路关联响应帧。
可选的，为更好地理解本申请实施例提供的非共址多链路设备的关联方法，下面从Non-AP MLD与AP MLD之间的交互角度进行说明。参见图16，图16是本申请实施例提供的Non-AP MLD与AP MLD的一交互示意图。如图16所示，AP MLD1包括AP11和AP12，AP MLD2包括AP21和AP22，Non-AP MLD包括STA1和STA2。其中，AP11和AP22可工作在5GHz频段上，AP12和AP22可工作在2.4GHz频段上；CH1@2.4GHz表示2.4GHz频段的信道1，CH1@5GHz表示5GHz频段的信道1，同理，CH2@2.4GHz表示2.4GHz频段的信道2，CH2@5GHz表示5GHz频段的信道2。如图16所示，Non-AP MLD在指示STA1与AP11之间的链路(link 11)状态为Disable，或Non-AP MLD断开STA1与AP11之间的链路(link 11)后，Non-AP MLD的STA1向AP MLD2发送Multi-link Association Request；AP MLD2的AP22向AP MLD1的AP12发送MLD Setup Request，请求建立一个Non-collocated MLD3；AP MLD1的AP12向AP MLD2的AP22返回MLD Setup Response，用于响应MLD Setup Request；AP MLD2向Non-AP MLD的STA1返回Multi-link Association Response，用于响应Multi-link Association Request。
可选的，MLD Setup Response响应MLD Setup Request的方式包括同意或拒绝。如果MLD Setup Response指示同意建立一个Non-collocated MLD3，则AP22和AP12可以共用一个高MAC层，或者说AP22和AP12组成一个新的逻辑多链路设备(即Non-collocated MLD3)。在后续配置等过程中，可以给AP22和AP12分配统一的序列号、PTK等。可理解的，在此场景下，Non-AP MLD可以看作从AP MLD1切换到Non-collocated MLD3。
其中，本申请实施例的步骤S201和步骤S204的实现方式可参考本申请实施例一中的步骤S101和步骤S102的实现方式，在此不再赘述。
可选的，多链路建立请求中可以携带以下信息：Non-AP MLD中STA1的相关信息和Non-collocated MLD3的相关信息。多链路建立响应中可以携带以下信息：状态码(Status code)和Non-collocated MLD3的相关信息。可理解的，AP22与AP11通过多链路建立请求和多链路建立响应来协商Non-collocated MLD3的相关信息。其中，STA1的相关信息可以包括STA1的SAP MAC Address、STA1的MAC Address指示以及锚链(Anchor link)指示等。Non-collocated MLD3的相关信息可以包括Non-collocated MLD3的SAP MAC Address、AP MLD2的AP22对应的链路信息以及AP MLD1的AP12对应的链路信息。
在多链路建立请求中，AP MLD2的AP22对应的链路信息可以包括链路标识符(Link ID),操作类别(Operating class),信道编号(Channel number),基本服务集标识(BSSID)以及AP22的其他相关信息；AP MLD1的AP12对应的链路信息可以包括Link ID,Operating class,Channel number,BSSID等。在多链路建立响应中，AP MLD2的AP22对应的链路信息可以包括Link ID,Operating class,Channel number,BSSID等；AP MLD1的AP12对应的链路信息可以包括Link ID,Operating class,Channel number,BSSID以及AP 12的其他相关信息。
本申请实施例在Non-AP MLD与AP MLD2的试探性关联过程中通过多链路建立请求和响应来建立Non-collocated MLD3，从而实现Non-AP MLD与Non-collocated MLD3之间的关联，可以提供一种最优关联场景下的关联方法。
上述内容详细阐述了本申请提供的方法，为了便于更好地实施本申请实施例的上述方案，本申请实施例还提供了相应的装置或设备。
本申请实施例可以根据上述方法示例对站点多链路设备或接入点多链路设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，参见图17，图17是本申请实施例提供的通信装置的一结构示意图。该通信装置1可以为Non-AP MLD或Non-AP MLD中的芯片，比如Wi-Fi芯片等。如图17所示，该通信装置1包括：处理单元11和收发单元12。
处理单元11，用于生成多链路关联请求帧；收发单元12，用于向一个或多个第二AP MLD发送多链路关联请求帧，该多链路关联请求帧用于发起Non-AP MLD与一个或多个第二AP MLD之间的多链路试探性关联；该收发单元12，还用于在Non-AP MLD与一个或多个第二AP MLD的多链路试探性关联成功的情况下，向目标AP MLD发送指示信息，用于触发目标AP MLD更新站点与接入点的映射关系，该目标AP MLD为从一个或多个第二AP MLD中确定出的第二AP MLD。
在一种可能的设计中，上述收发单元12还用于：向第一AP MLD发送链路状态指示信息，该链路状态指示信息用于指示Non-AP MLD的一个或多个第一STA与第一AP MLD之间的链路状态为断开状态。
本申请实施例的通信装置1具有上述方法中Non-AP MLD的任意功能，此处不再赘述。
参见图18，图18是本申请实施例提供的通信装置的另一结构示意图。该通信装置2可以为目标AP MLD或目标AP MLD中的芯片，比如Wi-Fi芯片等。如图18所示，该通信装置2包括：收发单元21和处理单元22。
收发单元21，用于接收来自Non-AP MLD的多链路关联请求帧，该多链路关联请求帧用于请求Non-AP MLD与目标AP MLD进行多链路试探性关联；该收发单元21，还用于当目标AP MLD返回的多链路关联响应帧指示关联成功时，从Non-AP MLD接收指示信息，该指示信息用于触发目标AP MLD更新站点与接入点的映射关系；处理单元22，用于生成站点与接入点的映射信息；该收发单元21，还用于发送站点与接入点的映射信息，该站点与接入点的映射信息用于指示站点与接入点的映射关系从Non-AP MLD与第一AP MLD关联更新为Non-AP MLD与目标AP MLD关联。
本申请实施例的通信装置2具有上述方法中目标AP MLD的任意功能，此处不再赘述。
以上介绍了本申请实施例的Non-AP MLD和目标AP MLD，以下介绍所述Non-AP MLD和目标AP MLD可能的产品形态。应理解，但凡具备上述图17所述的Non-AP MLD的功能的任何形态的产品，和但凡具备上述图18所述的目标AP MLD的功能的任何形态的产品，都落入本申请实施例的保护范围。还应理解，以下介绍仅为举例，不限制本申请实施例的Non-AP MLD和目标AP MLD的产品形态仅限于此。
作为一种可能的产品形态，本申请实施例所述的Non-AP MLD和目标AP MLD，可以 由一般性的总线体系结构来实现。
Non-AP MLD，包括处理器和与所述处理器内部连接通信的收发器。所述处理器用于生成多链路关联请求帧，该收发器用于向一个或多个第二AP MLD发送多链路关联请求帧，该多链路关联请求帧用于发起Non-AP MLD与一个或多个第二AP MLD之间的多链路试探性关联；该收发器，还用于在Non-AP MLD与一个或多个第二AP MLD的多链路试探性关联成功的情况下，向目标AP MLD发送指示信息，用于触发目标AP MLD更新站点与接入点的映射关系，该目标AP MLD为从一个或多个第二AP MLD中确定出的第二AP MLD。可选地，Non-AP MLD还可以包括存储器，所述存储器用于存储处理器执行的指令。
目标AP MLD，包括处理器和与所述处理器内部连接通信的收发器。所述收发器用于接收来自Non-AP MLD的多链路关联请求帧，该多链路关联请求帧用于请求Non-AP MLD与目标AP MLD进行多链路试探性关联；该收发器，还用于当目标AP MLD返回的多链路关联响应帧指示关联成功时，从Non-AP MLD接收指示信息，该指示信息用于触发目标AP MLD更新站点与接入点的映射关系，所述处理器用于生成站点与接入点的映射信息，该收发器，还用于发送站点与接入点的映射信息，该站点与接入点的映射信息用于指示站点与接入点的映射关系从Non-AP MLD与第一AP MLD关联更新为Non-AP MLD与目标AP MLD关联。可选地，目标AP MLD还可以包括存储器，所述存储器用于存储处理器执行的指令。
作为一种可能的产品形态，本申请实施例所述的Non-AP MLD和目标AP MLD，可以由通用处理器来实现。
实现Non-AP MLD的通用处理器包括处理电路和与所述处理电路内部连接通信的输入输出接口。所述处理电路用于生成多链路关联请求帧，该输入输出接口用于向一个或多个第二AP MLD发送多链路关联请求帧，该多链路关联请求帧用于发起Non-AP MLD与一个或多个第二AP MLD之间的多链路试探性关联；该输入输出接口，还用于在Non-AP MLD与一个或多个第二AP MLD的多链路试探性关联成功的情况下，向目标AP MLD发送指示信息，用于触发目标AP MLD更新站点与接入点的映射关系，该目标AP MLD为从一个或多个第二AP MLD中确定出的第二AP MLD。可选地，该通用处理器还可以包括存储介质，所述存储介质用于存储处理电路执行的指令。
实现目标AP MLD的通用处理器包括处理电路和与所述处理电路内部连接通信的输入输出接口。该输入输出接口用于接收来自Non-AP MLD的多链路关联请求帧，该多链路关联请求帧用于请求Non-AP MLD与目标AP MLD进行多链路试探性关联；该输入输出接口，还用于当目标AP MLD返回的多链路关联响应帧指示关联成功时，从Non-AP MLD接收指示信息，该指示信息用于触发目标AP MLD更新站点与接入点的映射关系；该处理电路用于生成站点与接入点的映射信息；该输入输出接口，还用于发送站点与接入点的映射信息，该站点与接入点的映射信息用于指示站点与接入点的映射关系从Non-AP MLD与第一AP MLD关联更新为Non-AP MLD与目标AP MLD关联。可选地，该通用处理器还可以包括存储介质，所述存储介质用于存储处理电路执行的指令。
作为一种可能的产品形态，本申请实施例所述的Non-AP MLD和目标AP MLD，还可以使用下述来实现：一个或多个FPGA(现场可编程门阵列)、PLD(可编程逻辑器件)、控制 器、状态机、门逻辑、分立硬件部件、任何其它适合的电路、或者能够执行本申请通篇所描述的各种功能的电路的任意组合。
应理解，上述各种产品形态的序列生成装置，具有上述方法实施例中Non-AP MLD的任意功能，此处不再赘述；上述各种产品形态的序列接收装置，具有上述方法实施例中AP MLD的任意功能，此处不再赘述。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序代码，当上述处理器执行该计算机程序代码时，电子设备执行前述任一实施例中的方法。
本申请实施例还提供一种计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行前述任一实施例中的方法。
本申请实施例还提供一种通信装置，该装置可以以芯片的产品形态存在，该装置的结构中包括处理器和接口电路，该处理器用于通过接收电路与其它装置通信，使得该装置执行前述任一实施例中的方法。
本申请实施例还提供一种无线通信系统，包括至少一个站点多链路设备和至少两个接入点多链路设备，该站点多链路设备和接入点多链路设备可以执行前述任一实施例中的方法。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机可读存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (26)

  1. 一种多链路试关联方法，其特征在于，包括：
    Non-AP MLD生成多链路关联请求帧；
    所述Non-AP MLD的一个或多个第一STA向一个或多个第二AP MLD发送多链路关联请求帧，所述多链路关联请求帧用于请求所述Non-AP MLD与所述一个或多个第二AP MLD进行多链路试探性关联，所述第一STA与第一AP MLD之间的链路状态为断开状态、且所述Non-AP MLD的第二STA与所述第一AP MLD之间的链路状态为连接状态；
    在所述Non-AP MLD与所述一个或多个第二AP MLD的多链路试探性关联成功的情况下，所述Non-AP MLD向目标AP MLD发送指示信息，所述指示信息用于触发所述目标AP MLD更新站点与接入点的映射关系，所述目标AP MLD为从所述一个或多个第二AP MLD中确定出的第二AP MLD。
  2. 一种多链路试关联方法，其特征在于，包括：
    目标AP MLD从Non-AP MLD接收多链路关联请求帧，所述多链路关联请求帧用于请求所述Non-AP MLD与所述目标AP MLD进行多链路试探性关联；
    在所述目标AP MLD与所述Non-AP MLD的多链路试探性关联成功的情况下，所述目标AP MLD从所述Non-AP MLD接收指示信息，所述指示信息用于触发所述目标AP MLD更新站点与接入点的映射关系；
    所述目标AP MLD生成并发送站点与接入点的映射信息，所述站点与接入点的映射信息用于指示站点与接入点的映射关系从所述Non-AP MLD与第一AP MLD关联更新为所述Non-AP MLD与所述目标AP MLD关联。
  3. 根据权利要求2所述的方法，其特征在于，所述站点与接入点的映射信息中包括所述Non-AP MLD的服务接入点SAP媒体接入控制MAC地址、和所述目标AP MLD的SAP MAC地址。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述指示信息携带于A-控制字段中。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述指示信息携带于通知帧中。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述多链路关联请求帧中包括所述Non-AP MLD与所述第二AP MLD之间的非传输链路的链路状态。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述多链路关联请求帧中还包括原因码字段，所述原因码字段用于指示所述Non-AP MLD的所述第二STA与所述第二AP MLD之间的链路状态为断开状态的原因。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述多链路关联请求帧还包括试探性关联指示信息，所述试探性关联指示信息用于指示是否进行多链路试探性关联。
  9. 根据权利要求8所述的方法，其特征在于，所述多链路关联请求帧还包括试探性关联生命期信息，所述试探性关联生命期信息用于指示所述多链路试探性关联的生命周期。
  10. 根据权利要求9所述的方法，其特征在于，所述试探性关联指示信息和所述试探性 关联生命期信息携带于多链路聚合MLA元素的公共信息字段中。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述Non-AP MLD的一个或多个第一STA向一个或多个第二AP MLD发送多链路关联请求帧之前，所述方法还包括：
    所述Non-AP MLD向第一AP MLD发送链路状态指示信息，所述链路状态指示信息用于指示所述Non-AP MLD的一个或多个第一STA与所述第一AP MLD之间的链路状态为断开状态。
  12. 根据权利要求11所述的方法，其特征在于，所述链路状态指示信息还用于指示所述第一STA与所述第一AP MLD之间的链路状态为断开状态的原因。
  13. 根据权利要求12所述的方法，其特征在于，所述第一STA与所述第一AP MLD之间的链路状态为断开状态的原因包括试探性关联。
  14. 一种通信装置，其特征在于，应用于Non-AP MLD中，包括：
    处理单元，用于生成多链路关联请求帧；
    收发单元，用于向一个或多个第二AP MLD发送多链路关联请求帧，所述多链路关联请求帧用于请求所述Non-AP MLD与所述一个或多个第二AP MLD进行多链路试探性关联，所述Non-AP MLD的一个或多个第一STA与第一AP MLD之间的链路状态为断开状态、且所述Non-AP MLD的第二STA与所述第一AP MLD之间的链路状态为连接状态；
    所述收发单元，还用于在所述Non-AP MLD与所述一个或多个第二AP MLD的多链路试探性关联成功的情况下，向目标AP MLD发送指示信息，所述指示信息用于触发所述目标AP MLD更新站点与接入点的映射关系，所述目标AP MLD为从所述一个或多个第二AP MLD中确定出的第二AP MLD。
  15. 一种通信装置，其特征在于，应用于目标AP MLD中，包括：
    收发单元，用于从Non-AP MLD接收多链路关联请求帧，所述多链路关联请求帧用于请求所述Non-AP MLD与所述目标AP MLD进行多链路试探性关联；
    所述收发单元，还用于在所述目标AP MLD与所述Non-AP MLD的多链路试探性关联成功的情况下，从所述Non-AP MLD接收指示信息，所述指示信息用于触发所述目标AP MLD更新站点与接入点的映射关系；
    处理单元，用于生成站点与接入点的映射信息；
    所述收发单元，还用于发送所述站点与接入点的映射信息，所述站点与接入点的映射信息用于指示站点与接入点的映射关系从所述Non-AP MLD与第一AP MLD关联更新为所述Non-AP MLD与所述目标AP MLD关联。
  16. 根据权利要求15所述的通信装置，其特征在于，所述站点与接入点的映射信息中包括所述Non-AP MLD的服务接入点SAP媒体接入控制MAC地址、和所述目标AP MLD的SAP MAC地址。
  17. 根据权利要求14-16任一项所述的通信装置，其特征在于，所述指示信息携带于A-控制字段中。
  18. 根据权利要求14-17任一项所述的通信装置，其特征在于，所述指示信息携带于通知帧中。
  19. 根据权利要求14-18任一项所述的通信装置，其特征在于，所述多链路关联请求帧中包括所述Non-AP MLD与所述第二AP MLD之间的非传输链路的链路状态。
  20. 根据权利要求14-19任一项所述的通信装置，其特征在于，所述多链路关联请求帧中还包括原因码字段，所述原因码字段用于指示所述Non-AP MLD的所述第二STA与所述第二AP MLD之间的链路状态为断开状态的原因。
  21. 根据权利要求14-20任一项所述的通信装置，其特征在于，所述多链路关联请求帧还包括试探性关联指示信息，所述试探性关联指示信息用于指示是否进行多链路试探性关联。
  22. 根据权利要求21所述的通信装置，其特征在于，所述多链路关联请求帧还包括试探性关联生命期信息，所述试探性关联生命期信息用于指示所述多链路试探性关联的生命周期。
  23. 根据权利要求22所述的通信装置，其特征在于，所述试探性关联指示信息和所述试探性关联生命期信息携带于多链路聚合MLA元素的公共信息字段中。
  24. 根据权利要求14所述的通信装置，其特征在于，所述收发单元还用于：
    向第一AP MLD发送链路状态指示信息，所述链路状态指示信息用于指示所述Non-AP MLD的一个或多个第一STA与所述第一AP MLD之间的链路状态为断开状态。
  25. 根据权利要求24所述的通信装置，其特征在于，所述链路状态指示信息还用于指示所述第一STA与所述第一AP MLD之间的链路状态为断开状态的原因。
  26. 根据权利要求25所述的通信装置，其特征在于，所述第一STA与所述第一AP MLD之间的链路状态为断开状态的原因包括试探性关联。
PCT/CN2021/095343 2020-05-27 2021-05-21 多链路试关联方法及相关装置 WO2021238823A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP21812460.0A EP4145947A4 (en) 2020-05-27 2021-05-21 PROVISIONAL MULTI-LINK ASSOCIATION METHOD AND ASSOCIATED APPARATUS

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202010463544 2020-05-27
CN202010463544.7 2020-05-27
CN202010550151.XA CN113747502A (zh) 2020-05-27 2020-06-16 多链路试关联方法及相关装置
CN202010550151.X 2020-06-16

Publications (1)

Publication Number Publication Date
WO2021238823A1 true WO2021238823A1 (zh) 2021-12-02

Family

ID=78727974

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/095343 WO2021238823A1 (zh) 2020-05-27 2021-05-21 多链路试关联方法及相关装置

Country Status (3)

Country Link
EP (1) EP4145947A4 (zh)
CN (1) CN113747502A (zh)
WO (1) WO2021238823A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114765901A (zh) * 2021-12-20 2022-07-19 成都极米科技股份有限公司 多链路设备连接管理方法、装置、设备及存储介质
EP4203560A1 (en) * 2021-12-23 2023-06-28 INTEL Corporation Enhanced wi-fi fast roaming transition for mobile devices
EP4216607A1 (en) * 2022-01-24 2023-07-26 Avago Technologies International Sales Pte. Limited Seamless roaming of multi-radio station
EP4250819A1 (en) * 2022-03-25 2023-09-27 Intel Corporation Enhanced roaming operations with reordering using scoreboard sharing for non-collocated wi-fi multi-link devices
WO2023231422A1 (zh) * 2022-05-30 2023-12-07 中兴通讯股份有限公司 non-AP MLD的通信方法、装置、存储介质及电子装置
CN117858203A (zh) * 2024-03-08 2024-04-09 广东九安智能科技股份有限公司 一种无线视频监控自动选网方法和系统
WO2024092050A1 (en) * 2022-10-26 2024-05-02 Qualcomm Incorporated Multi-link-based roaming

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116600368B (zh) * 2022-02-18 2024-03-01 华为技术有限公司 Emlsr模式下链路状态指示方法及相关装置
CN116801318A (zh) * 2022-03-18 2023-09-22 展讯通信（上海）有限公司 数据传输方法、装置、芯片、芯片模组及电子设备
CN114630368B (zh) * 2022-04-22 2023-03-24 成都极米科技股份有限公司 控制在多链路上进行数据传输的方法、装置、设备及介质
AU2023203520B2 (en) 2022-04-24 2024-02-08 Huawei Technologies Co., Ltd. Multi-link communication setup method and related apparatus
WO2024065461A1 (zh) * 2022-09-29 2024-04-04 Oppo广东移动通信有限公司 多链路通信的方法及设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190158413A1 (en) * 2017-11-17 2019-05-23 Qualcomm Incorporated Link aggregation with floating primary link
US20190335454A1 (en) * 2018-07-11 2019-10-31 Po-Kai Huang Methods for multi-link setup between a multi-link access point (ap) logical entity and a multi-link non-ap logical entity
CN110536482A (zh) * 2018-09-28 2019-12-03 中兴通讯股份有限公司 一种节点之间链路连接管理的方法及相关设备
US20200037288A1 (en) * 2018-08-10 2020-01-30 Po-Kai Huang Block acknowledgement and fragmentation in multi-link communication between multi-link logical entities
WO2020040589A1 (ko) * 2018-08-23 2020-02-27 엘지전자 주식회사 무선랜 시스템에서 통신을 수행하기 위한 링크를 설정하기 위한 방법 및 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190158413A1 (en) * 2017-11-17 2019-05-23 Qualcomm Incorporated Link aggregation with floating primary link
US20190335454A1 (en) * 2018-07-11 2019-10-31 Po-Kai Huang Methods for multi-link setup between a multi-link access point (ap) logical entity and a multi-link non-ap logical entity
US20200037288A1 (en) * 2018-08-10 2020-01-30 Po-Kai Huang Block acknowledgement and fragmentation in multi-link communication between multi-link logical entities
WO2020040589A1 (ko) * 2018-08-23 2020-02-27 엘지전자 주식회사 무선랜 시스템에서 통신을 수행하기 위한 링크를 설정하기 위한 방법 및 장치
CN110536482A (zh) * 2018-09-28 2019-12-03 中兴通讯股份有限公司 一种节点之间链路连接管理的方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4145947A4

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114765901A (zh) * 2021-12-20 2022-07-19 成都极米科技股份有限公司 多链路设备连接管理方法、装置、设备及存储介质
CN114765901B (zh) * 2021-12-20 2023-05-02 极米科技股份有限公司 多链路设备连接管理方法、装置、设备及存储介质
EP4203560A1 (en) * 2021-12-23 2023-06-28 INTEL Corporation Enhanced wi-fi fast roaming transition for mobile devices
EP4216607A1 (en) * 2022-01-24 2023-07-26 Avago Technologies International Sales Pte. Limited Seamless roaming of multi-radio station
EP4250819A1 (en) * 2022-03-25 2023-09-27 Intel Corporation Enhanced roaming operations with reordering using scoreboard sharing for non-collocated wi-fi multi-link devices
WO2023231422A1 (zh) * 2022-05-30 2023-12-07 中兴通讯股份有限公司 non-AP MLD的通信方法、装置、存储介质及电子装置
WO2024092050A1 (en) * 2022-10-26 2024-05-02 Qualcomm Incorporated Multi-link-based roaming
CN117858203A (zh) * 2024-03-08 2024-04-09 广东九安智能科技股份有限公司 一种无线视频监控自动选网方法和系统

Also Published As

Publication number Publication date
EP4145947A1 (en) 2023-03-08
CN113747502A (zh) 2021-12-03
EP4145947A4 (en) 2023-11-22

Similar Documents

Publication Publication Date Title
WO2021238823A1 (zh) 多链路试关联方法及相关装置
JP7312813B2 (ja) ｎｏｎ－ＡＰマルチバンド通信装置、通信方法及び集積回路
US9433022B2 (en) Method and apparatus for filtering-based scanning in WLAN system
US11924823B2 (en) Multi-link device association and reassociation
WO2013166907A1 (zh) 网络接入方法及装置
US11882514B2 (en) Communications method and communications apparatus
US11206576B2 (en) Rapidly disseminated operational information for WLAN management
KR101873391B1 (ko) Ap에 접속된 sta에 대한 재연관 시간 감소
US20160021609A1 (en) Method for setting up high-speed link in wlan system and apparatus for same
KR101629339B1 (ko) 무선랜 시스템에서 고속 링크 동기화 방법 및 장치
TWI805263B (zh) 直連鏈路定址方法及裝置
WO2022253791A1 (en) Communication methods, device and non-transitory computer-readable medium to signal emlmr links and associated emlmr links sets
JP2024511921A (ja) マルチリンクオペレーションのための管理リンク
US20150078358A1 (en) Method and apparatus for setting up high-speed link in wlan system
CN116234069B (zh) 多链路的重配置方法及装置
WO2024065461A1 (zh) 多链路通信的方法及设备
WO2023138497A1 (zh) 通信方法、接入点多链路设备和非接入点多链路设备
KR20220020947A (ko) 다중 액세스포인트 보조 전송 방법, 장치, 저장 매체 및 전자 장치

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: 21812460

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021812460

Country of ref document: EP

Effective date: 20221202

NENP Non-entry into the national phase

Ref country code: DE