Roaming method, communication network, related device and storage medium

Abstract

Provided in the embodiments of the present application are a roaming method, a communication network, a related device and a storage medium, which enable a terminal device to roam seamlessly from a first AP MLD to a second AP MLD and effectively reduce roaming latency. The roaming method is applied to a communication network, wherein the communication network comprises L access point multi-link devices (AP MLDs), the multiple links supported by a first AP MLD include a first link, and the multiple links supported by a second AP MLD include a second link. The method comprises: a first AP MLD sending an association message to a second AP MLD, wherein the association message corresponds to a terminal device, and the association message is used for the first AP MLD to communicate with the terminal device on a first link; and the first AP MLD deactivating the first link, wherein the association message is further used for the second AP MLD to communicate with the terminal device on a second link.

Description

A roaming method, a communication network, related equipment, and a storage medium.

[0001] This application claims priority to Chinese Patent Application No. 202411550358.1, filed with the State Intellectual Property Office of China on October 31, 2024, entitled "A roaming method, communication network, related equipment and storage medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a roaming method, communication network, related equipment, and storage medium. Background Technology

[0003] An access point multi-link device (AP MLD) is a wireless local area network (WLAN) device that simultaneously supports multiple links (ML).

[0004] A non-access point multi-link device (non-AP MLD) communicates with the original access point (AP MLD) via multiple links. In roaming scenarios, the original AP MLD first needs to close the first link with the non-AP MLD (one of the multiple links supported by the original AP MLD). The non-AP MLD then establishes a second link with the target AP MLD (also one of the multiple links supported by the target AP MLD). After the second link is established, the non-AP MLD and the target AP MLD communicate via this second link.

[0005] When a non-AP MLD roams to the second link of the target AP MLD, the non-AP MLD and the target AP MLD need to perform access processes such as re-association, four-way handshake, and re-aggregation, which increases the latency of non-AP MLD roaming. Summary of the Invention

[0006] This application provides a roaming method, communication network, related equipment, and storage medium, which enables a terminal device to roam seamlessly from a first AP MLD to a second AP MLD and effectively reduces roaming latency.

[0007] In a first aspect, this application provides a roaming method applied to a communication network, the communication network including L access point multi-link devices (AP MLDs), where L is any integer greater than or equal to 2, the first AP MLD supports a first link among multiple links, and the second AP MLD supports a second link among multiple links, the method comprising: the first AP MLD sending an association message to the second AP MLD, the association message corresponding to a terminal device, the association message being used for the first AP MLD to communicate with the terminal device on the first link; the first AP MLD closing the first link, the association message also being used for the second AP MLD to communicate with the terminal device on the second link.

[0008] As illustrated in this aspect, the signal coverage of the first AP MLD is limited. As the location of the terminal device changes, the terminal device will gradually leave the currently connected first AP MLD and enter the signal range of the second AP MLD. Because the first AP MLD sends an association message to the second AP MLD, the second AP MLD can achieve seamless roaming to the second link of the second AP MLD without the terminal device needing to re-execute the probing process, authentication process, association process, key exchange, aggregation process, etc., effectively reducing roaming latency and ensuring the continuity of communication between the terminal device and the AP MLD with virtually no packet loss, thus improving communication efficiency.

[0009] Based on the first aspect, in one optional implementation, the Media Access Control Layer MAC address of the first AP MLD is the same as the MAC address of the second AP MLD. Among the L AP MLDs, the first AP MLD is different from the second AP MLD. The Basic Service Set Identifier (BSSID) of the first link is the same as the BSSID of the second link, and the identifier of the first link is the same as the identifier of the second link.

[0010] With this implementation, since the MAC address of the first AP MLD is the same as that of the second AP MLD, the BSSID of the first link is the same as that of the second link, and the identifier of the first link is the same as that of the second link, when the second AP MLD receives the association message from the first AP MLD, the terminal device does not need to re-execute the probing process, authentication process, association process, key exchange, aggregation process, etc. with the second AP MLD, effectively reducing roaming latency.

[0011] Based on the first aspect, in one optional implementation, the first AP MLD supports a third link among multiple links. After the first AP MLD sends an association message to the second AP MLD, the method further includes: the first AP MLD communicating with the terminal device on the third link based on the association message.

[0012] By adopting this implementation method, during the process of the terminal device seamlessly roaming from the first link to the second link, the terminal device and the first AP MLD continue to communicate through the third link. This avoids the situation where the remaining links between the terminal device and the first AP MLD are disconnected due to the terminal device seamlessly roaming from the first link to the second link, thus ensuring multi-link transmission between the terminal device and the first AP MLD.

[0013] Based on the first aspect, in one optional implementation, the second AP MLD further includes a fourth link among the multiple links supported by the second AP MLD. After the first AP MLD sends an association message to the second AP MLD, the method further includes: the first AP MLD closing the third link.

[0014] Using this implementation, the terminal device can seamlessly roam from the third link of the first AP MLD to the fourth link of the second AP MLD, achieving multi-link transmission while reducing roaming latency.

[0015] Based on the first aspect, in one optional implementation, the BSSID of the third link is the same as the BSSID of the fourth link, and the identifier of the third link is the same as the identifier of the fourth link.

[0016] By adopting this implementation method, since the BSSID of the third link is the same as that of the fourth link, and the identifier of the third link is the same as that of the fourth link, it is effectively guaranteed that the terminal device can achieve seamless roaming from the third link to the fourth link.

[0017] Based on the first aspect, in an optional implementation, before the first AP MLD shuts down the first link, the method further includes: the first AP MLD obtaining a first configuration message, the first configuration message carrying a target media access control layer MAC address, a target basic service set identifier (BSSID), and a target identifier, wherein the MAC address of the second AP MLD is the target MAC address, the BSSID of the second link is the target BSSID, and the identifier of the second link is the target identifier; the first AP MLD, according to the first configuration message, configures its MAC address as the target MAC address, configures the BSSID of the first link as the target BSSID, and configures the identifier of the first link as the target identifier.

[0018] This implementation effectively ensures that the MAC address of the first AP MLD is the same as that of the second AP MLD, the BSSID of the first link is the same as that of the second link, and the identifier of the first link is the same as that of the second link. Therefore, when the second AP MLD receives the association message from the first AP MLD, the terminal device does not need to re-execute the probing process, authentication process, association process, key exchange, aggregation process, etc. with the second AP MLD. This achieves the goal of seamless roaming to the second link of the second AP MLD, effectively reducing roaming latency and ensuring the continuity of communication between the terminal device and the AP MLD with virtually no packet loss, thereby improving communication efficiency.

[0019] Based on the first aspect, in one optional implementation, the first AP MLD obtaining the first configuration message includes: the first AP MLD receiving the first configuration message from the master control device, wherein the master control device is connected to the first AP MLD and the second AP MLD respectively; or, the first AP MLD receiving the first configuration message from the second AP MLD; or, the first AP MLD locally generating the first configuration message.

[0020] By adopting this implementation method, the reliability of the first AP MLD obtaining the first configuration message can be guaranteed, thereby improving the success rate of seamless roaming.

[0021] Based on the first aspect, in an optional implementation, after the first AP MLD obtains the first configuration message, the method further includes: the first AP MLD sending a second configuration message to the second AP MLD, the second configuration message carrying the target MAC address, the target BSSID, the target identifier, and the identifier of the second AP MLD.

[0022] In this implementation, the first AP MLD sends a second configuration message to the second AP MLD to ensure that the MAC address of the first AP MLD is the same as that of the second AP MLD, the BSSID of the first link is the same as that of the second link, and the identifier of the first link is the same as that of the second link, thereby improving the reliability of seamless roaming.

[0023] Based on the first aspect, in an optional implementation, the first configuration message further carries at least one of an encryption key, a target service set identifier (SSID), a password, an encryption method, a channel bandwidth, and a wireless standard; wherein, the terminal device uses the encryption key to access the first link, the SSID of the wireless network to which the first link belongs is the target SSID, the terminal device authenticates with the first AP MLD based on the password, the encryption method is the encryption method for data transmission on the first link, the channel bandwidth is the channel bandwidth of the first link, and the wireless standard is the wireless standard supported by the first link.

[0024] In this implementation, the first configuration message carries a variety of information to ensure that the terminal device can successfully roam seamlessly from the first link to the second link, thereby improving the reliability of seamless roaming and reducing the latency of seamless roaming.

[0025] Based on the first aspect, in an optional implementation, the first AP MLD closing the first link includes: the first AP MLD deleting the first link; or, the first link of the first AP MLD not being used to send downlink messages to the terminal device, and the first AP MLD discarding uplink messages received from the terminal device via the first link; or, the first link of the first AP MLD not being used to send downlink messages to any terminal device, and the first AP MLD discarding uplink messages received from any terminal device via the first link.

[0026] By adopting this implementation method, the first AP MLD can promptly shut down the first link when it determines that the terminal device has seamlessly roamed from the first link to the second link, thereby improving the success rate of seamless roaming of the terminal device.

[0027] Based on the first aspect, in an optional implementation, before the first AP MLD shuts down the first link, the method further includes: the first AP MLD receiving a shutdown indication message, the shutdown indication message being used to instruct the first AP MLD to shut down the first link, the shutdown indication message carrying at least one of the BSSID of the first link, the identifier of the first link, and the identifier of the terminal device.

[0028] Using this implementation, the first AP MLD can promptly shut down the first link based on the shutdown instruction information, reducing the latency of seamless roaming.

[0029] Based on the first aspect, in an optional implementation, after the first AP MLD closes the first link, the method further includes: the first AP MLD sending a link switching request to the second AP MLD, the link switching request being used to instruct the terminal device to roam from the first link to the second link, the link switching request being used to request the second AP MLD to open the second link, the link switching request carrying at least one of the BSSID of the first link and the identifier of the first link, and the link switching request also carrying the identifier of the terminal device.

[0030] Using this implementation, the terminal device will not be aware of the seamless roaming process from the first link to the second link. During the seamless roaming process, the service between the terminal device and the AP MLD is in a normal transmission state, avoiding service transmission interruption and ensuring communication continuity.

[0031] Based on the first aspect, in an optional implementation, after the first AP MLD shuts down the first link, the method further includes: the first AP MLD sending a link shutdown feedback message to the master control device, the link shutdown feedback message being used to indicate that the first AP MLD has shut down the first link, the link shutdown feedback message carrying at least one of the BSSID of the first link and the identifier of the first link, and the link shutdown feedback message also carrying the identifier of the terminal device.

[0032] In this implementation, when the first AP MLD closes link1, the first AP MLD sends a link closure feedback message to the master control device. The first link closure feedback message is used to indicate that the first AP MLD has closed link1, so that the master control device can determine based on the first link closure feedback message that the first link between the first AP MLD and the target non-AP MLD has been closed by the first AP MLD, thereby triggering the master control device to instruct the second AP MLD to open link2, thus ensuring that the terminal device can seamlessly roam from the first link to the second link.

[0033] Based on the first aspect, in an optional implementation, after the first AP MLD sends an association message to the second AP MLD, the method further includes: the first AP MLD instructing the terminal device to delete the first link; and the first AP MLD instructing the terminal device to add the second link.

[0034] In this implementation, the first AP MLD negotiates with the terminal device to instruct the terminal device to delete the first link and add the second link, thereby ensuring that the terminal device can successfully and seamlessly roam from the first link to the second link.

[0035] Based on the first aspect, in an optional implementation, after the first AP MLD sends an association message to the second AP MLD, the method further includes: the first AP MLD sending a reconfiguration notification, the reconfiguration notification being used to notify the deletion of the first link; the first AP MLD receiving a first link reconfiguration request from the terminal device, the first link reconfiguration request being used to request the deletion of the first link; and the first AP MLD sending a link reconfiguration response to the terminal device, the link reconfiguration response being used to indicate the deletion of the first link.

[0036] Using this implementation, the first AP MLD instructs the terminal device to delete the first link through a reconfiguration notification, thereby improving the reliability of seamless roaming.

[0037] Based on the first aspect, in one optional implementation, the reconfiguration notification is a first link reconfiguration notification. Sending the reconfiguration notification by the first AP MLD includes: the first AP MLD sending the first link reconfiguration notification to the terminal device. The first link reconfiguration notification carries the identifier of the terminal device and a link deletion indication, and the first link reconfiguration notification carries at least one of the identifier of the first link and the BSSID. The link deletion indication is used to indicate the deletion of the first link.

[0038] In this implementation, the first AP MLD sends a first link reconfiguration notification directly to the terminal device to instruct the terminal device to delete the first link, thereby ensuring the reliability of seamless roaming.

[0039] Based on the first aspect, in an optional implementation, the reconfiguration notification is a deletion instruction message. The first AP MLD sending the reconfiguration notification includes: the first AP MLD sending the deletion instruction message to the second AP MLD. The deletion instruction message is used to instruct the second AP MLD to send a first link reconfiguration notification to the terminal device. The first link reconfiguration notification carries the identifier of the terminal device and a link deletion instruction, and the first link reconfiguration notification carries at least one of the identifier of the first link and the BSSID. The link deletion instruction is used to instruct the deletion of the first link.

[0040] In this implementation, the first AP MLD sends a deletion instruction message to the second AP MLD, instructing the second AP MLD to send a first link reconfiguration notification to the terminal device, thereby notifying the terminal device to delete the first link and ensuring the reliability of seamless roaming.

[0041] Based on the first aspect, in an optional implementation, after the first AP MLD closes the first link, the method further includes: the first AP MLD sending a shutdown indication frame to the terminal device, the shutdown indication frame being a beacon frame or a probe response frame, the shutdown indication frame being used to indicate that the first AP MLD has closed the first link; the first AP MLD receiving a first link reconfiguration request from the terminal device, the first link reconfiguration request being used to request the deletion of the first link; and the first AP MLD sending a link reconfiguration response to the terminal device, the link reconfiguration response being used to indicate the deletion of the first link.

[0042] In this implementation, the first AP MLD sends a shutdown instruction frame to the terminal device to enable the terminal device to delete the first link, thereby ensuring the reliability of seamless roaming.

[0043] Based on the first aspect, in an optional implementation, after the first AP MLD sends an association message to the second AP MLD, the method further includes: the first AP MLD sending a second link reconfiguration notification to the terminal device, the second link reconfiguration notification being used to notify the terminal device to add the second link, the second link reconfiguration notification carrying the identifier of the terminal device, and the second link reconfiguration notification carrying at least one of the identifier of the second link and the BSSID.

[0044] In this implementation, the first AP MLD sends a second link reconfiguration notification directly to the terminal device to enable the terminal device to add a second link, thereby ensuring the reliability of seamless roaming.

[0045] Based on the first aspect, in an optional implementation, after the first AP MLD sends an association message to the second AP MLD, the method further includes: the first AP MLD sending a link reconfiguration notification to the second AP MLD, the link reconfiguration notification being used to notify the second AP MLD to enable the second link, the link reconfiguration notification carrying the identifier of the terminal device, and the link reconfiguration notification carrying at least one of the identifier of the second link and the BSSID.

[0046] In this implementation, the first AP MLD sends a link reconfiguration notification to the second AP MLD to enable the terminal device to add a second link, thereby ensuring the reliability of seamless roaming.

[0047] Based on the first aspect, in one optional implementation, the first link is the link with the fastest signal attenuation speed among the multiple links supported by the first AP MLD, or the first link is the link with the lowest signal quality among the multiple links supported by the first AP MLD, or the first link is the link with the largest bandwidth usage among the multiple links supported by the first AP MLD.

[0048] By adopting this implementation method, a link that meets certain conditions is selected as the first link to be switched, which can effectively suppress the reduction of communication efficiency while achieving seamless roaming.

[0049] Based on the first aspect, in an optional implementation, the associated message includes at least one of the following: association information, authentication information, aggregated session information, physical layer parameters, identity authentication information of the terminal device, link information, encryption key, aggregation information, packet sequence number PN, sequence number SN, group temporary key GTK, and communication context information.

[0050] By adopting this implementation method, the terminal device can be seamlessly roamed from the first link to the second link by using associated messages carrying multiple types of information, thus ensuring the success rate of seamless roaming and reducing the latency of seamless roaming.

[0051] Secondly, this application provides a roaming method applied to a communication network, the communication network including L Access Point Multi-Link Devices (AP MLDs), where L is any integer greater than or equal to 2, the first AP MLD supports a first link among multiple links, and the second AP MLD supports a second link among multiple links, the method comprising: the second AP MLD receiving an association message from the first AP MLD, the association message corresponding to a terminal device, the association message being used by the first AP MLD to communicate with the terminal device on the first link; the second AP MLD activating the second link, the association message also being used by the second AP MLD to communicate with the terminal device on the second link. For an explanation of the beneficial effects of this aspect, please refer to the first aspect, which will not be elaborated further.

[0052] Based on the second aspect, in an optional implementation, the first AP MLD supports a third link among the multiple links, and the second AP MLD supports a fourth link among the multiple links. After the second AP MLD receives the association message from the first AP MLD, the method further includes: the second AP MLD activating the fourth link, and the association message is also used for the second AP MLD to communicate with the terminal device on the fourth link.

[0053] Based on the second aspect, in an optional implementation, before the second AP MLD activates the second link, the method further includes: the second AP MLD obtaining a second configuration message, the second configuration message carrying a target MAC address, a target BSSID, and a target identifier, wherein the MAC address of the first AP MLD is the target MAC address, the BSSID of the first link is the target BSSID, and the identifier of the first link is the target identifier; the second AP MLD, according to the second configuration message, configures the MAC address of the second AP MLD to the target MAC address, configures the BSSID of the second link to the target BSSID, and configures the identifier of the second link to the target identifier.

[0054] Based on the second aspect, in one optional implementation, the second AP MLD obtaining the second configuration message includes: the second AP MLD receiving the second configuration message from the master control device, wherein the master control device is connected to both the first AP MLD and the second AP MLD; or, the second AP MLD receiving the second configuration message from the first AP MLD; or, the second AP MLD locally generating the second configuration message.

[0055] Based on the second aspect, in an optional implementation, after the second AP MLD obtains the second configuration message, the method further includes: the second AP MLD sending a first configuration message to the first AP MLD, the first configuration message carrying the target MAC address, the target BSSID, the target identifier, and the identifier of the first AP MLD.

[0056] Based on the second aspect, in one optional implementation, the second AP MLD activating the second link includes: the second AP MLD adding the second link; or, the second link of the second AP MLD being used to send downlink messages to the terminal device, and the second AP MLD receiving uplink messages from the terminal device via the second link; or, the second link of the second AP MLD having the capability to send downlink messages to any terminal device, and the second AP MLD having the capability to receive uplink messages from any terminal device via the second link.

[0057] Based on the second aspect, in an optional implementation, before the second AP MLD activates the second link, the method further includes: the second AP MLD sending a shutdown indication message to the first AP MLD, the shutdown indication message being used to indicate that the first AP MLD shuts down the first link, the shutdown indication message carrying at least one of the BSSID of the first link, the identifier of the first link, and the identifier of the terminal device.

[0058] Based on the second aspect, in an optional implementation, the second AP MLD activating the second link includes: the second AP MLD receiving a link switching request, the link switching request being used to instruct the terminal device to roam from the first link to the second link, the link switching request carrying at least one of the BSSID of the first link and the identifier of the first link, the link switching request also carrying the identifier of the terminal device; the second AP MLD activating the second link according to the link switching request.

[0059] Based on the second aspect, in an optional implementation, after the second AP MLD receives the association message from the first AP MLD, the method further includes: the second AP MLD instructing the terminal device to delete the first link; and the second AP MLD instructing the terminal device to add the second link.

[0060] Based on the second aspect, in an optional implementation, after the second AP MLD receives the association message from the first AP MLD, the method further includes: the second AP MLD receiving a deletion instruction message; the second AP MLD sending a first link reconfiguration notification to the terminal device according to the deletion instruction message, the first link reconfiguration notification carrying the identifier of the terminal device and a link deletion instruction, and the first link reconfiguration notification carrying at least one of the identifier of the first link and the BSSID, the link deletion instruction being used to indicate the deletion of the first link; the second AP MLD receiving a first link reconfiguration request from the terminal device, the first link reconfiguration request being used to request the deletion of the first link; the second AP MLD sending a link reconfiguration response to the terminal device, the link reconfiguration response being used to indicate the deletion of the first link.

[0061] Based on the second aspect, in an optional implementation, after the second AP MLD activates the second link, the method further includes: the second AP MLD receiving a second link reconfiguration request from the terminal device, the second link reconfiguration request being used to request the addition of the second link, the second link reconfiguration request carrying the identifier of the terminal device, and the second link reconfiguration request carrying at least one of the identifier of the second link and the BSSID; the second AP MLD sending a second link reconfiguration response to the terminal device, the second link reconfiguration response being used to indicate the addition of the second link.

[0062] Based on the second aspect, in an optional implementation, before the second AP MLD receives the second link reconfiguration request from the terminal device, the method further includes: the second AP MLD sending a second link reconfiguration notification to the terminal device, the second link reconfiguration notification being used to notify the terminal device to add the second link, the second link reconfiguration notification carrying the identifier of the terminal device, and the second link reconfiguration notification carrying at least one of the identifier of the second link and the BSSID.

[0063] Based on the second aspect, in an optional implementation, the second AP MLD activating the second link includes: the second AP MLD receiving a link reconfiguration notification, the link reconfiguration notification carrying the identifier of the terminal device, and the link reconfiguration notification carrying at least one of the identifier of the second link and the BSSID; the second AP MLD activating the second link according to the link reconfiguration notification; after the second AP MLD activates the second link, the method further includes: the second AP MLD sending an add instruction to the terminal device according to the link reconfiguration notification, the add instruction being used to indicate the addition of the second link.

[0064] Based on the second aspect, in an optional implementation, after the second AP MLD receives the association message from the first AP MLD, the method further includes: the second AP MLD sending an activation indication frame to the terminal device, the activation indication frame being a beacon frame or a probe response frame, the activation indication frame being used to indicate that the second AP MLD has activated the second link; the second AP MLD receiving a first link reconfiguration request from the terminal device, the first link reconfiguration request being used to request the deletion of the first link; and the second AP MLD sending a link reconfiguration response to the terminal device, the link reconfiguration response being used to indicate the deletion of the first link.

[0065] Thirdly, this application provides a roaming method applied to a communication network, the communication network including a master control device and L access point multi-link devices (AP MLDs), where L is any integer greater than or equal to 2. The master control device is connected to a first AP MLD and a second AP MLD respectively. The first AP MLD supports multiple links, including a first link, and the second AP MLD supports multiple links, including a second link. The method includes: the master control device receiving an association message from the first AP MLD, the association message corresponding to a terminal device, the association message being used for the first AP MLD to communicate with the terminal device on the first link; the master control device sending the association message to the second AP MLD; the master control device sending a first shutdown indication message to the first AP MLD, the first shutdown indication message being used to instruct the first AP MLD to shut down the first link; and the master control device sending a first activation indication message to the second AP MLD, the first activation indication message being used to instruct the second AP MLD to activate the second link, the association message being used for the second AP MLD to communicate with the terminal device on the second link. For an explanation of the beneficial effects of this aspect, please refer to the first aspect, which will not be elaborated further.

[0066] Fourthly, this application provides a communication network including L Access Point Multi-Link Devices (AP MLDs), where L is any integer greater than or equal to 2. The first AP MLD supports a first link among its multiple links, and the second AP MLD supports a second link among its multiple links. The first AP MLD is configured to: send an association message to the second AP MLD, the association message corresponding to a terminal device, the association message being used by the first AP MLD to communicate with the terminal device on the first link; and close the first link. The second AP MLD is configured to open the second link, the association message also being used by the second AP MLD to communicate with the terminal device on the second link.

[0067] Based on the fourth aspect, in an optional implementation, the communication network further includes a master control device, which is connected to the first AP MLD and the second AP MLD respectively. The master control device is used to instruct the first AP MLD to close the first link and to instruct the second AP MLD to open the second link.

[0068] Fifthly, this application provides an Access Point Multilink Device (AP MLD), the AP MLD including a processor and a transceiver, wherein the processor is used to perform any of the processing-related actions in the first aspect described above, and the transceiver is used to perform any of the sending-receiving-receiving actions in the first aspect described above; or, the processor is used to perform any of the processing-related actions in the second aspect described above, and the transceiver is used to perform any of the sending-receiving-receiving-receiving actions in the second aspect described above.

[0069] In a sixth aspect, this application provides an Access Point Multilink Device (AP MLD), the AP MLD including a module for performing any of the methods described in the first aspect above, or the AP MLD including a module for performing any of the methods described in the second aspect above.

[0070] In a seventh aspect, this application provides a chip including a logic circuit and a communication interface. The communication interface is used to receive data and transmit it to the logic circuit, or to send data from the logic circuit to another chip. The logic circuit is used to perform any of the processing-related actions described in the first aspect, and the communication interface is used to perform any of the transmission-reception-related actions described in the first aspect. Alternatively, the logic circuit is used to perform any of the processing-related actions described in the second aspect, and the communication interface is used to perform any of the transmission-reception-related actions described in the second aspect. The logic circuit is used to perform any of the processing-related actions described in the third aspect, and the communication interface is used to perform any of the transmission-reception-related actions described in the third aspect.

[0071] Eighthly, this application provides a computer-readable storage medium including computer program instructions that, when executed by a processor, perform the method as described in any of the first aspects above, or the method as described in any of the second aspects above, or the method as described in any of the third aspects above.

[0072] Ninthly, this application provides a computer program product comprising computer program code, which, when run on a computer, causes the computer to perform the method described in any of the first aspects, or to perform the method described in any of the second aspects, or to perform the method described in any of the third aspects. Attached Figure Description

[0073] Figure 1a is a structural example diagram of a first embodiment of the communication network provided in this application;

[0074] Figure 1b is a structural example diagram of a second embodiment of the communication network provided in this application;

[0075] Figure 2 is a structural example diagram of a second embodiment of the communication network provided in this application;

[0076] Figure 3 is a flowchart of the steps of the first embodiment of the roaming method provided in this application;

[0077] Figure 4 is a first configuration example of the access device provided in this application;

[0078] Figure 5 is a specific configuration example shown in Figure 4;

[0079] Figure 6a is a second configuration example of the access device provided in this application;

[0080] Figure 6b is a third configuration example of the access device provided in this application;

[0081] Figure 7 is a flowchart of the steps of a second embodiment of the roaming method provided in this application;

[0082] Figure 8 is a flowchart of the steps of a third embodiment of the roaming method provided in this application;

[0083] Figure 9 is a flowchart of the steps of the fourth embodiment of the roaming method provided in this application;

[0084] Figure 10 is a first structural example of the wireless local area network device provided in this application;

[0085] Figure 11 is a second structural example of the wireless local area network device provided in this application;

[0086] Figure 12 is a schematic diagram of one embodiment of the chip provided in this application. Detailed Implementation

[0087] Figure 1a is a structural example diagram of a first embodiment of the communication network provided in this application. The communication network 100 shown in this embodiment includes N access devices, specifically access device 101, access device 102, and so on up to access device 10N, where N is any integer greater than or equal to 2. The communication network 100 also includes one or more terminal devices. For example, the communication network 100 shown in Figure 1a includes terminal device 110 that has been connected to access device 101. This embodiment does not limit the number of terminal devices included in the communication network 100. Each access device shown in Figure 1a is an access point (AP). Each AP includes one or more AP MLDs. For example, AP101 includes AP MLD131, and AP102 includes AP MLD141. This embodiment does not limit the number of AP MLDs included in each AP. For example, the communication network includes L AP MLDs, where L can be any integer greater than or equal to N. Taking AP MLD131 as an example, AP MLD can also be called a multi-link AP, multi-link AP device, or other names, without specific limitations. AP MLD131 refers to a wireless local area network (WLAN) device that simultaneously supports multiple links (ML). AP MLD131 has the ability to send and receive data on multiple links, thereby enabling AP101 and terminal device 110 to use greater bandwidth for service transmission, thus significantly improving throughput (extremely high throughput, EHT). In addition, multiple links are very helpful in reducing latency and improving robustness. For example, different links can be as shown in the following examples: Example 1, different links have different access frequencies. Example 2, different links have different access frequency bands. Among them, the frequency bands include, but are not limited to, all or part of the 2.4 GHz band, 5 GHz band, 6 GHz band, and high-frequency 60 GHz band supported by Wireless Fidelity (Wi-Fi). Optionally, any two access points (APs) in the communication network 100 shown in this embodiment can be connected, for example, via fiber optic cable, Wi-Fi, Ethernet, near field communication (NFC), infrared, Bluetooth, or ZigBee, etc., without any specific limitation.

[0088] Each Access Point (AP) can be a device deployed in a communication network to provide wireless communication functionality to its associated terminal devices. These are primarily deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. Outdoor deployments are also possible. An AP acts as a bridge connecting wired and wireless networks, its main function being to connect various terminal devices and then connect the communication network to the Ethernet. Specifically, each AP can be any type of communication device, such as a base station with a Wi-Fi chip, router, gateway, repeater, communication server, switch, bridge, or customer premises equipment (CPE) in a digital subscriber line (DSL) network. Base stations can include various forms of macro base stations, micro base stations, and repeater stations. When APs are used in WLAN applications, they can implement wireless communication according to the 802.11 series of standards, including 802.11be, 802.11ax, 802.11a / b / g / n / ac, or next-generation standards, without specific limitations. Of course, this application can also be applied to other possible communication networks, such as narrowband Internet of Things (NB-IoT) systems, long term evolution (LTE) systems, 5th generation mobile communication technology (5G), 6th generation mobile communication technology (6G), or future mobile communication technologies. It should be understood that the above description is merely illustrative of communication networks, and the communication networks to which this application applies are not limited to these examples; they will not be described in detail here.

[0089] This embodiment does not limit the number of terminal devices included in the communication network. Taking terminal device 110 as an example, a non-AP MLD supports communication with the AP via multiple links. Specifically, AP MLD 131 of AP 101 includes AP interface 132 and AP interface 133, and non-AP MLD 110 includes Station (STA) interface 111 and STA interface 112. AP interface 132 and STA interface 111 are connected via a first link (hereinafter referred to as link1), allowing communication between non-AP MLD 110 and AP 101. AP interface 133 and STA interface 112 are connected via a third link (hereinafter referred to as link3), allowing communication between non-AP MLD 110 and AP 101 via link3.

[0090] In this embodiment, the non-AP MLD110 can be a wireless communication chip, a wireless sensor, or a wireless communication terminal. Examples include user terminals, user equipment, access devices, subscriber stations, subscriber units, mobile stations, user agents, and user equipment that support Wi-Fi communication, without limitation. The non-AP MLD can include various handheld devices, vehicle-mounted devices, wearable devices, Internet of Things (IoT) devices, artificial intelligence (AI) terminals, virtual reality (VR) terminals, computing devices, wearable devices, or other processing devices connected to a wireless modem, as well as various forms of user equipment (UE), mobile stations (MS), terminals, non-AP MLDs (terminal equipment), portable communication devices, handheld devices, portable computing devices, entertainment devices, gaming devices or systems, GPS devices, or any other suitable devices configured for network communication via wireless media. In addition, the non-AP MLD can support the 802.11be standard or the next-generation WLAN standard of 802.11be. The non-AP MLD can also support multiple WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.

[0091] Optionally, the communication network 100 shown in this embodiment further includes a master control device 120, which is connected to each AP and used for centralized configuration, monitoring, and management of each AP. For example, the master control device 120 may be an access controller (AC). This embodiment takes the example of the master control device 120 being separate from each AP; in other examples, the master control device 120 may be located inside one or more APs.

[0092] Figure 1a shows an example of an AP including an AP MLD, for example, AP101 including AP MLD131. Figure 1b is a structural example of a second embodiment of the communication network provided in this application. In the example shown in Figure 1b, the communication network 200 includes P roaming AP MLDs, for example, the communication network 200 includes Roaming AP MLD201, Roaming AP MLD202, and so on up to Roaming AP MLD20P, where P is any integer greater than or equal to 2. The communication network 200 also includes one or more AP MLDs connected to Roaming AP MLD201, for example, Roaming AP MLD201 is connected to AP MLD231 and AP MLD232. Roaming AP MLD201 and AP MLD231 are two independent physical devices, and Roaming AP MLD201 and AP MLD232 are two independent physical devices. For a description of the AP MLD structure, please refer to Figure 1a, which will not be elaborated further. Taking AP MLD231 as an example, AP MLD231 and Roaming AP MLD201 can be connected via wired or wireless connections. Wired connections include, but are not limited to, telephone lines, network cables, or coaxial cables, while wireless connections include, but are not limited to, Wi-Fi, Ethernet, NFC, infrared, Bluetooth, or ZigBee. The media access control (MAC) address of AP MLD231 and the MAC address of AP MLD232 both use the MAC address of Roaming AP MLD201. Therefore, the MAC addresses of Roaming AP MLD201, AP MLD231, and AP MLD232 are the same. The communication network 200 also includes one or more AP MLDs connected to Roaming AP MLD202. For example, Roaming AP MLD202 connects to AP MLD233 and AP MLD234. It can be understood that the MAC addresses of AP MLD233 and AP MLD234 are both the MAC address of Roaming AP MLD202. Similarly, the communication network 200 also includes one or more AP MLDs connected to the Roaming AP MLD20P. For example, the Roaming AP MLD20P connects to AP MLD235 and AP MLD236. It can be understood that the MAC address of AP MLD235 and the MAC address of AP MLD236 are both the MAC address of the Roaming AP MLD20P.The description of the communication network 200, including the non-AP MLD 210 and the main control device 220, is shown in Figure 1a, and will not be elaborated further.

[0093] Figures 1a and 1b illustrate the application of the communication network as an optional example and are not intended to limit it. For example, the communication network can also be applied to fiber to the room (FTTR). Referring to Figure 2, which is a structural example diagram of a second embodiment of the communication network provided in this application.

[0094] Building upon Fiber to the Home (FTTH), to address Wi-Fi coverage, the fiber optic cable can be extended further into the homes of residents. Terminal devices providing Wi-Fi access are installed inside these rooms, reducing the distance between the terminal devices and the Wi-Fi access point and improving signal quality. This application scenario is called FTTR. Specifically, Figure 2 illustrates the system architecture of FTTR. FTTR and FTTH networks can be viewed as cascaded passive optical network (PON) systems. In FTTH, the optical line terminal (OLT) is deployed in the center office (CO), while the optical network unit (ONU) or optical network terminal (ONT) is deployed in the home's information box. The master device in FTTR can replace the ONU or ONT in FTTH. This master device in the FTTR scenario has similar functions to the OLT in the FTTH scenario, and it can also have similar functions to the ONU or ONT in the FTTH scenario. In other words, the master device in an FTTR is a device that combines the functions of an OLT and an ONU, serving as a bridge between FTTH and FTTR. The slave devices in an FTTR can be deployed in various rooms of the home to connect with terminal devices. These slave devices are essentially similar to the ONUs or ONTs in an FTTH. Since the slave devices in the FTTR are located in each room and can directly connect to terminal devices via Wi-Fi, they can be either the AP shown in Figure 1a or the AP MLD shown in Figure 1b. Terminal devices can connect to the slave devices and transmit data through the established Wi-Fi connection. Alternatively, the master device can specifically be a main FTTR unit (MFU), and the slave devices can specifically be sub-FTTR units (SFUs). The MFU can be connected to one or more SFUs via optical fiber. The MFU interacts with the SFU through a Wi-Fi management and control channel (WMCC) and a Wi-Fi management and control interface (WMCI). The master device can also be called a "master gateway," "master optical modem," or "master FTTR device," etc., and the slave device can also be called a "slave gateway," "slave optical modem," or "slave FTTR device," etc. This application does not limit their specific names.

[0095] It is understood that Figures 1a and 2 are only schematic diagrams. The communication network may also include other equipment, such as wavelength division multiplexing equipment, optical amplifiers, and more terminal equipment, which are not shown in Figures 1a and 2.

[0096] Based on the communication network described above, this application provides a roaming method that enables seamless roaming. Seamless roaming is also referred to as zero handover, seamless roaming, etc. The specific name is not limited in this embodiment. Specifically, seamless roaming can control the seamless roaming time of a non-AP MLD between multiple AP MLDs to the millisecond level, with virtually no packet loss. This ensures that when a non-AP MLD switches from one AP MLD to another during seamless roaming, the non-AP MLD maintains a stable connection, and the non-AP MLD will hardly feel any interruption or pause, thus improving communication efficiency. Referring again to Figures 1a and 1b, the non-AP MLD 110 is connected to links 1 and 3 of the first AP MLD 131. Using the method shown in this embodiment, the non-AP MLD 110 can seamlessly roam to the second AP MLD 141. Specifically, the non-AP MLD 110 switches from link 1 to link 2, where link 2 is the link connecting the AP interface 142 and the STA interface 111 of the second AP MLD 141. The non-AP MLD 110 switches from link 3 to link 4, where link 4 is the link connecting the AP interface 143 and the STA interface 112 of the second AP MLD 141. For a detailed explanation of links 2 and 4, please refer to the explanation of links 1 and 2 shown above, which will not be repeated here. The AP MLD executing the roaming method shown in this embodiment can be the AP MLD itself, or a processor, chip, chip system, logic module running on the processor, software, or device running an operating system included in the AP MLD. The non-AP MLD that executes the roaming method shown in this embodiment can be the non-AP MLD itself, or a processor, chip, chip system, logic module running on the processor, software, or device running an operating system included in the non-AP MLD. See Figure 3 for details, which is a flowchart of the first embodiment of the roaming method provided in this application.

[0097] Step 301: The AC sends the first configuration message to the first AP MLD.

[0098] Step 302: The AC sends a second configuration message to the second AP MLD.

[0099] This embodiment uses the AC as the master control device as an example, and the execution timing between steps 301 and 302 is not limited. Example 1, referring to Figure 1a, shows a communication network including ACs separate from each AP. The AC will send a first configuration message to the first AP MLD and a second configuration message to the second AP MLD. For example, the first AP MLD could be AP MLD131 included in AP101, and the second AP MLD could be AP MLD141 included in AP102. The timing of the AC sending the first and second configuration messages is not limited. Both the first and second configuration messages carry the target MAC address, the target basic service set identifier (BSSID), and the target identifier. Therefore, the first AP MLD configures its MAC address as the target MAC address according to the first configuration message, and the second AP MLD configures its MAC address as the target MAC address according to the second configuration message. It can be understood that the MAC address of the first configured AP MLD is the same as the MAC address of the second configured AP MLD, and both are target MAC addresses. According to the first configuration message, the first AP MLD configures the BSSID of link1 supported by the first AP MLD as the target BSSID, and the second AP MLD configures the BSSID of link2 supported by the second AP MLD as the target BSSID. It can also be understood that the BSSID of link1 supported by the first configured AP MLD is the same as the BSSID of link2 supported by the second configured AP MLD, and both are target BSSIDs. link1 is one of multiple links supported by the first AP MLD, and link2 is one of multiple links supported by the second AP MLD. For a description of link2, please refer to the description of link1 shown above; details will not be repeated here. According to the first configuration message, the first AP MLD configures the identifier (ID) of link1 supported by the first AP MLD as the target ID, and the second AP MLD configures the ID of link2 supported by the second AP MLD as the target ID. It is understandable that the ID of link1 supported by the first configured AP MLD is the same as the ID of link2 supported by the second configured AP MLD, and both are target IDs.

[0100] The first configuration message shown in this embodiment also carries the identifier of the first AP MLD to ensure that the first configuration message can be successfully transmitted to the first AP MLD. The identifier of the first AP MLD can be its ID, MAC address, Internet Protocol (IP) address, etc. The second configuration message also carries the identifier of the second AP MLD to ensure that the second configuration message can be successfully transmitted to the second AP MLD. For an explanation of the second AP MLD identifier, please refer to the explanation of the first AP MLD identifier; details will not be repeated here.

[0101] Example 2, referring to Figure 1b, shows that the first AP MLD can be AP MLD231, and the second AP MLD can be AP MLD233. It can be understood that the first AP MLD and the second AP MLD are connected to different Roaming AP MLDs. The AC sends a first configuration message to Roaming AP MLD201, which forwards the message to AP MLD231. The AC sends a second configuration message to Roaming AP MLD202, which forwards the message to AP MLD233. Based on the first configuration message, Roaming AP MLD201 configures its MAC address as the target MAC address. For a description of the first and second configuration messages, please refer to Example 1; further details are omitted here. Roaming AP MLD201 configures its MAC address as the target MAC address according to the first configuration message, and Roaming AP MLD202 configures its MAC address as the target MAC address according to the second configuration message. It can be understood that since the MAC address of the first AP MLD is the same as the MAC address of Roaming AP MLD201, and the MAC address of the second AP MLD is the same as the MAC address of Roaming AP MLD202, the MAC addresses of the first and second AP MLDs are the same, and both are target MAC addresses. The process of the first AP MLD configuring according to the first configuration message and the second AP MLD configuring according to the second configuration message is shown in Example 1, and will not be elaborated further. This example uses the first AP MLD and the second AP MLD connecting to different Roaming AP MLDs. In other examples, the first AP MLD and the second AP MLD can connect to the same Roaming AP MLD, and there is no specific limitation.

[0102] The method shown in this embodiment is applied to the communication network shown in Figure 1a as an example. This embodiment uses the example of the AC sending a first configuration message to the first AP MLD and a second configuration message to the second AP MLD, respectively. This is not limited to specific examples. For instance, the AC sends the first configuration message to the first AP MLD, and the first AP MLD then forwards the second configuration message to the second AP MLD. For explanations of the first and second configuration messages, please refer to the example above; specific details will not be repeated here. Similarly, the AC can also send the second configuration message to the second AP MLD, and the second AP MLD then forwards the first configuration message to the first AP MLD. For example, if the first AP MLD can perform the functions of the AC, then the first AP MLD configures itself according to the first configuration message it receives, and then sends the second configuration message to the second AP MLD. Optionally, the first AP MLD may not need to reconfigure the MAC address, link1 BSSID, and ID, but can directly send the second configuration message to the second AP MLD. The second configuration message carries the target MAC address of the first AP MLD, the target BSSID of link1 supported by the first AP MLD, and the target ID of link1 supported by the first AP MLD. Similarly, the second AP MLD can also perform AC functionality. The second AP MLD configures itself according to the second configuration message it receives, and then sends the first configuration message to the first AP MLD. Optionally, the second AP MLD does not need to reconfigure the MAC address, link2 BSSID, and ID; instead, it directly sends the first configuration message to the first AP MLD. The first configuration message carries the target MAC address of the second AP MLD, the target BSSID of link2 supported by the second AP MLD, and the target ID of link2 supported by the second AP MLD.

[0103] It should be clarified that the information carried in the first configuration message and the second configuration message in this embodiment may also include the information types shown below. This embodiment does not limit the information types carried in the first configuration message and the second configuration message, as long as the first AP MLD is configured according to the first configuration message, and the second AP MLD is configured according to the second configuration message, the terminal device can seamlessly roam from link1 of the first AP MLD to link2 of the second AP MLD. The first configuration message and the second configuration message also carry encryption keys, target service set identifiers (SSIDs), passwords, encryption methods, channel bandwidth, and wireless standards, respectively.

[0104] Both link1 and link2 correspond to the encryption key. Terminal devices can successfully connect to either link1 or link2 using this encryption key. Different terminal devices connect to link1 using different encryption keys, and similarly, different terminal devices connect to link2 using different encryption keys. The target SSID is the SSID of both link1 and link2. It can be understood that the SSID of link1 in the configured first AP MLD is the same as the SSID of link2 in the configured second AP MLD, and both are the target SSID. The password is used for terminal devices to authenticate through the first AP MLD and the second AP MLD. If the terminal device connects to link1, the encryption method is the same as the encryption method used for data transmitted between the first AP MLD and the terminal device via link1. If the terminal device connects to link2, the encryption method is the same as the encryption method used for data transmitted between the second AP MLD and the terminal device via link2. This embodiment does not limit the type of encryption method. For example, encryption methods include, but are not limited to, no encryption (OPEN), Wi-Fi protected access (WPA), Wi-Fi protected access version 2 (WPA2), Wi-Fi protected access version 3 (WPA3), Temporal key integrity protocol (TKIP), and advanced encryption standard (AES). The channel bandwidth is the channel bandwidth supported by link1 and link2. The wireless standards supported by link1 and link2 include, but are not limited to, 11N (also known as the wireless LAN communication standard IEEE 802.11n-2009), 11ac, Wi-Fi 7, Wi-Fi 8, or next-generation WLAN standards.

[0105] The first AP MLD and the second AP MLD shown in this embodiment both include multiple AP interfaces. The first configuration message and the second configuration message shown in this embodiment are also used to configure the AP interfaces included in the first AP MLD and the AP interfaces included in the second AP MLD. For the method of configuring the AP interfaces, please refer to the following:

[0106] This example uses a static configuration method, as shown in Figure 4. Figure 4 is a first configuration example diagram of the access device provided in this application.

[0107] The first configuration message obtained by the first AP is also used to indicate the AP MLD corresponding to each non-AP MLD included in the communication network. The first AP is configured according to the first configuration message so that the configured first AP includes one or more AP MLDs corresponding to each non-AP MLD. In this example, the communication network includes M non-AP MLDs. Then, the M non-AP MLDs can be non-AP MLD401, non-AP MLD402, and so on up to non-AP MLD40M, where M is any integer greater than or equal to 1. Taking non-AP MLD401 as an example, non-AP MLD401, non-AP MLD402, and non-AP MLD40M all correspond to AP MLD421. Figure 5 is a specific configuration example diagram shown in Figure 4. AP MLD421 includes multiple AP interfaces. The example shown in Figure 5 is that the first AP MLD421 configures the first AP interface 521 and the third AP interface 523 according to the first configuration message. Each AP interface is implemented through software modules included in the first AP MLD421, and different AP interfaces support different links. Specifically, the first AP interface 521 supports link 1, and the third AP interface 523 supports link 3. The first AP interface 521 and the third AP interface 523 are two of the K AP interfaces included in the first AP MLD421. The example shown in Figure 5 uses the second AP MLD422 configuring the second AP interface 522 and the fourth AP interface 524 according to the second configuration message. Each AP interface is implemented through software modules included in the second AP MLD422, and different AP interfaces support different links. Specifically, the second AP interface 522 supports link 2, and the fourth AP interface 524 supports link 4. The second AP interface 522 and the fourth AP interface 524 are two of the K AP interfaces included in the second AP MLD422. Taking the non-AP MLD401, which includes STA interfaces 501 and 502, as an example, for an explanation of the non-AP MLD401 including STA interfaces, please refer to the explanation of the first AP MLD421 including AP interfaces; details will not be repeated here. As shown above, the first configuration message includes the target BSSID and the target identifier. Therefore, the BSSID of the first AP interface 521 configured by the first AP MLD according to the first configuration message is the target BSSID, thus making the BSSID of link1 supported by the first AP interface 521 the target BSSID. Similarly, the ID of the first AP interface 521 configured by the first AP MLD according to the first configuration message is the target ID, thus making the ID of link1 supported by the first AP interface 521 the target ID.When a non-AP MLD401 connects to the first AP MLD421, the first AP interface 521 and the STA interface 501 are connected via link1. The first AP interface 521 can also use the encryption key, target service set identifier (SSID), password, encryption method, channel bandwidth, and wireless standard included in the first configuration message to achieve communication with the non-AP MLD401. For instructions on configuring the third AP interface 523 on the first AP MLD421, please refer to the instructions on configuring the first AP interface 521 on the first AP MLD421; details will not be repeated here. It should be noted that this example uses different non-AP MLDs that all correspond to the same AP MLD421 in the first AP. Therefore, AP MLD421 can support multiple non-AP MLDs, meaning that AP MLD421 can establish links with multiple non-AP MLDs simultaneously. In other examples, different non-AP MLDs may correspond to different AP MLDs in the first AP, or different non-AP MLDs may correspond to partially identical AP MLDs in the first AP, etc., without specific limitations.

[0108] It is understandable that after the first AP MLD421 is configured according to the first configuration message, and the second AP MLD is configured according to the second configuration message, since the information carried in the first configuration message is the same as the information carried in the second configuration message, the AP MLD corresponding to non-AP MLD401, which is connected to the first AP MLD421, is the same on the first AP as on the second AP. Using the configuration method shown in this example, even if non-AP MLD401 is not connected to the second AP MLD422, the second AP is still configured with the second AP MLD422 corresponding to non-AP MLD401. Similarly, the AP MLD422 corresponding to non-AP MLD40M, which is connected to the second AP MLD422, is the same on the second AP as on the first AP MLD421. Even if non-AP MLD40M is not connected to the first AP MLD421, the first AP is still configured with the first AP MLD421 corresponding to non-AP MLD40M. For example, if a non-AP MLD402 that has been connected to the first AP MLD421 needs to seamlessly roam to the second AP MLD422, the AP MLD421 corresponding to the non-AP MLD402 on the first AP is the same as the second AP MLD422 corresponding to the non-AP MLD402. Even if the non-AP MLD402 fails to seamlessly roam to the second AP MLD422, the second AP will still be configured with the second AP MLD422 corresponding to the non-AP MLD402.

[0109] Figures 4 and 5 illustrate static configuration as an example, without limitation. For instance, the AP MLD can also be configured dynamically as shown below, as illustrated in Figure 6a, which is a second configuration example of the access device provided in this application.

[0110] In this example, the first AP includes AP MLD611 corresponding to non-AP MLD601, where non-AP MLD601 is a non-AP MLD already connected to the first AP. AP MLD611 supports K links connected to non-AP MLD601, enabling communication between the first AP and non-AP MLD601 through the K links. For a description of the AP MLD, please refer to Figures 4 and 5; further details are omitted here. Similarly, the first AP includes AP MLD621 corresponding to non-AP MLD602, where non-AP MLD602 is a non-AP MLD already connected to the first AP. AP MLD621 supports K links connected to non-AP MLD602, enabling communication between the first AP and non-AP MLD602 through the K links. The second AP includes an AP MLD631 corresponding to the non-AP MLD60M. The AP MLD631 is used to support K links connected to the non-AP MLD60M, so that the second AP and the non-AP MLD60M can communicate through the K links.

[0111] Figure 6b is a third configuration example diagram of the access device provided in this application. If the AC detects that non-AP MLD602 needs to be seamlessly roamed from the first AP to the second AP, the AC sends a second configuration message to the second AP, and the second AP configures the AP MLD621 corresponding to non-AP MLD602 according to the second configuration message. Optionally, the first configuration message sent by the AC to the first AP may carry an AP MLD deletion instruction, then the first AP deletes the AP MLD621 corresponding to non-AP MLD602 according to the AP MLD deletion instruction.

[0112] Combining the static configuration shown in Figure 4 with the dynamic configurations shown in Figures 6a and 6b, it can be seen that with static configuration, the AP MLD on each AP always exists and serves every non-AP MLD included in the communication network. For example, the first AP MLD on the first AP can simultaneously serve every non-AP MLD in the communication network. The communication network can add new AP MLDs as needed (for example, adding a third AP MLD based on the first and second AP MLDs). When adding a new third AP MLD, it is not necessary to configure an AP MLD with a new link ID and BSSID in the third AP MLD; that is, the link ID and BSSID corresponding to the third AP MLD can be the same as those corresponding to the first AP MLD. Therefore, the process of adding AP MLDs in the communication network is not limited by the range of link ID values. For example, the link ID value ranges from 0 to 14. Even if a new third AP MLD is added to the communication network, the link ID supported by the third AP MLD can reuse the link ID supported by the first AP MLD, improving the scalability of the communication network supported by this embodiment. Through dynamic configuration, the AP MLD on each AP only serves non-AP MLDs that have been connected to that AP MLD, or non-AP MLDs that are waiting to be seamlessly roamed to that AP MLD.

[0113] Step 303: The first AP MLD sends the associated message corresponding to the target non-AP MLD to the AC.

[0114] Step 304: The AC sends the associated message corresponding to the target non-AP MLD to the second AP MLD.

[0115] This embodiment uses the example of a related message being sent from the first AP MLD to the AC, and then forwarded by the AC to the second AP MLD. This is not a limitation; for example, if the AC detects that a target non-AP MLD needs to be seamlessly roamed from the first AP MLD to the second AP MLD, the AC obtains the related message corresponding to the target non-AP MLD from the first AP MLD, and then forwards the related message to the second AP MLD. Alternatively, the first AP MLD can directly send the related message corresponding to the target non-AP MLD to the second AP MLD.

[0116] The target non-AP MLD shown in this embodiment is one of multiple non-AP MLDs already connected to the first AP MLD, such as non-AP MLD 602 ​​shown in Figures 6a and 6b. The target non-AP MLD is currently connected to the first AP MLD. Since the target non-AP MLD is connected to the first AP MLD, a probing process, an authentication process, an association process, a key exchange process, and an aggregation process need to be performed between the target non-AP MLD and the first AP MLD. When the target non-AP MLD successfully connects to the first AP MLD, the first AP MLD stores the association message corresponding to the target non-AP MLD. Based on this association message, communication between the first AP MLD and the target non-AP MLD is achieved through multiple links. For example, the first AP MLD communicates with the target non-AP MLD on link1 and link3 based on the association message.

[0117] In this embodiment, the associated message corresponding to the target non-AP MLD may include, but is not limited to, association information, authentication information, aggregated session information, physical layer parameters, the target non-AP MLD's identity authentication information, link information, encryption key, packet part number (PN), sequence number (SN), group temporary key (GTK), communication context information, etc. It should be noted that this embodiment does not limit the specific content of the associated message, as long as the second AP MLD can seamlessly roam to the second AP MLD based on the associated message.

[0118] The association information refers to a series of parameters and status information exchanged when establishing a link between the target non-AP MLD and the first AP MLD. This embodiment does not limit the specific content of the association information; it is based on the ability to maintain and manage communication between the AP MLD and the target non-AP MLD, ensuring effective connection and communication between them. The authentication information stores the information exchanged during the authentication and authorization process between the target non-AP MLD and the first AP MLD, ensuring that the target non-AP MLD passes the authentication of the first AP MLD. The aggregation session information refers to the aggregation established between the target non-AP MLD and the first AP MLD for sending data packets. Physical layer parameters include information such as frequency, channel, and modulation scheme, to achieve purposes such as optimizing performance, increasing throughput, reducing latency, and enhancing robustness. The target non-AP MLD's authentication information includes its MAC address, IP address, and ID. Link information includes, but is not limited to, the identifiers and quality parameters of each link connecting the target non-AP MLD and the first AP MLD. The encryption key is used for encryption and decryption during service transmission between the first AP MLD and the target non-AP MLD, ensuring the security of service transmission. To ensure the continuity of service transmission between the target non-AP MLD and the AP MLD, the associated message also includes communication context information, which refers to the context information of service transmission on link1, the connection between the first AP MLD and the target non-AP MLD.

[0119] The signal coverage of the first AP MLD is limited, so the target non-AP MLD can only maintain a stable connection within the signal coverage area of ​​the first AP MLD. However, as the location of the target non-AP MLD changes, it will gradually leave the currently connected first AP MLD and enter the signal range of the second AP MLD. To ensure uninterrupted connection, the target non-AP MLD needs to seamlessly roam to the second AP MLD with a stronger and more stable signal. To ensure seamless roaming during the transition from the first AP MLD to the second AP MLD—that is, to maintain an uninterrupted connection during roaming without requiring the target non-AP MLD and the second AP MLD to re-initiate probing, authentication, association, key exchange, and aggregation processes—and thus achieve a high-throughput, low-latency seamless roaming process, the first AP MLD needs to synchronize the corresponding association message of the target non-AP MLD to the second AP MLD. For example, the first AP MLD directly sends the associated message corresponding to the target non-AP MLD to the second AP MLD. Or, the first AP MLD sends the associated message corresponding to the target non-AP MLD to the AC, and the AC then forwards the associated message corresponding to the target non-AP MLD to the second AP MLD. This embodiment does not limit the method by which the first AP MLD sends the associated message corresponding to the target non-AP MLD to the second AP MLD.

[0120] Because the MAC address of the first AP MLD shown in this embodiment is the same as the MAC address of the second AP MLD, the link IDs corresponding to the target non-AP MLD on the first AP MLD are the same as the link IDs corresponding to the target non-AP MLD on the second AP MLD, and the BSSIDs of the links corresponding to the target non-AP MLD on the first AP MLD are the same as the BSSIDs of the links corresponding to the target non-AP MLD on the second AP MLD. Moreover, when the target non-AP MLD seamlessly roams from the first AP MLD to the second AP MLD, the second AP MLD has already obtained the association message corresponding to the target non-AP MLD from the first AP MLD. Therefore, the target non-AP MLD does not need to re-execute the probing process, authentication process, association process, key exchange process, and aggregation process with the second AP MLD, ensuring that the target non-AP MLD can seamlessly roam to the second AP MLD.

[0121] Step 305: AC sends a first shutdown instruction message to the first AP MLD.

[0122] If the AC determines that a target non-AP MLD needs to seamlessly roam from the first AP MLD to the second AP MLD, the AC sends a first shutdown instruction message to the first AP MLD. This first shutdown instruction message instructs the first AP MLD to shut down link1. The first shutdown instruction message carries the identifier of the target non-AP MLD, enabling the first AP MLD to determine and shut down the link used for communication with the target non-AP MLD based on this identifier. The identifier of the target non-AP MLD includes at least one of its MAC address, IP address, or ID. The first shutdown instruction message also carries at least one of link1's ID and link1's BSSID, enabling the first AP MLD to determine that the specific link to be shut down is link1. This embodiment uses the AC sending a first shutdown instruction message to the first AP MLD as an example, and is not limited to this. For example, if the first AP MLD has AC functionality, it can detect that the target non-AP MLD needs to seamlessly roam from the first AP MLD to the second AP MLD, and thus directly shuts down link1. For example, the first AP MLD receives a first shutdown instruction message from the second AP MLD.

[0123] In this embodiment, link1 is one of multiple links connecting the first AP MLD to the target non-AP MLD, as shown in the following example:

[0124] Example 1: link1 is a random link among the multiple links supported by the first AP MLD.

[0125] Example 2: link1 is the fastest decaying link among the multiple links supported by the first AP MLD.

[0126] Example 3: Link1 is the link with the lowest transmission quality among the multiple links supported by the first AP MLD. The signal quality can be the received signal strength indication (RSSI), received channel power indicator (RCPI), transmission rate, reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), signal to interference plus noise ratio (SINR), throughput, or packet loss rate detected by the first AP MLD.

[0127] Example 4: link1 is the link that occupies the most bandwidth among the multiple links supported by the first AP MLD.

[0128] Step 306: The first AP MLD shuts down link1.

[0129] The first AP MLD shuts down link1 according to the first shutdown instruction message. The first AP MLD can shut down link1 in three ways:

[0130] Method 1: If each AP configures the AP MLD dynamically (see Figures 6a and 6b), then the way to disable link1 is to have the first AP delete the first AP interface included in the first AP MLD that provides link1, so that the first AP MLD cannot communicate with the target non-AP MLD via link1.

[0131] Method 2: If each AP configures its MLD in a static way (see Figure 4) or in a dynamic way (see Figures 6a and 6b), then the way the first AP MLD closes link1 is as follows: the first AP MLD controls link1 to not send downlink messages to any non-AP MLD, and if the first AP MLD receives an uplink message from any non-AP MLD through link1, the first AP MLD discards the uplink message.

[0132] Method 3: If each AP configures the AP MLD dynamically or statically, then the way the first AP MLD closes link1 is as follows: the first AP MLD controls itself not to send downlink messages to the target non-AP MLD, and if the first AP interface receives an uplink message from the target non-AP MLD through link1, the first AP MLD discards the uplink message from the target non-AP MLD.

[0133] Step 307: The first AP MLD sends a first link shutdown feedback message to the AC.

[0134] When the first AP MLD closes link1, it sends a first link closure feedback message to the AC. This message indicates that the first AP MLD has closed link1. The first link closure feedback message carries at least one of the BSSID and identifier of link1, and also carries the identifier of the target non-AP MLD. Based on this first link closure feedback message, the AC determines that link1 between the first AP MLD and the target non-AP MLD has been closed by the first AP MLD.

[0135] Step 308: The AC sends the first link switching request to the second AP MLD.

[0136] Upon receiving a first link shutdown feedback message, the AC sends a first link handover request to the second AP MLD. This first link handover request instructs the target non-AP MLD to seamlessly roam from link1 to link2. To ensure successful roaming of the target non-AP MLD, this first link handover request instructs the second AP MLD to enable link2. For example, the first link handover request carries the identifier of the target non-AP MLD, and also carries at least one of the link1 ID and the link1 BSSID.

[0137] This embodiment takes the AC sending a first link switching request to the second AP MLD as an example. In other examples, the first AP MLD can directly send the first link switching request to the second AP MLD.

[0138] Step 309: Enable link2 in the second AP MLD.

[0139] When the second AP MLD receives the first link switching request, the second AP MLD obtains at least one of the link1 ID and link1 BSSID carried in the first link switching request message. The method by which the second AP MLD enables link2 can be seen in the following optional methods:

[0140] Method 1: If the AP MLD is configured dynamically (see Figures 6a and 6b), then enabling link 2 involves configuring the second AP MLD to support link 2. For example, as shown in Figure 6b, non-AP MLD 602 ​​is the target non-AP MLD to be seamlessly roamed to the second AP MLD. The second AP configures AP MLD 621 according to the second configuration message, and AP MLD 621 communicates with the target non-AP MLD via its supported link 2.

[0141] Method 2: If the AP MLD is configured statically (see Figure 4) or dynamically (see Figures 6a and 6b), then link2 is enabled as follows: the second AP MLD controls link2 and has the authority to send downlink messages to any non-AP MLD. When the second AP MLD receives an uplink message from any non-AP MLD through link2, the second AP MLD processes the uplink message and does not discard it.

[0142] Method 3: If the AP MLD is configured dynamically or statically, then the way to enable link2 is that the second AP MLD controls link2 and has the authority to send downlink messages to the target non-AP MLD. When the second AP MLD receives uplink messages from the target non-AP MLD through link2, the second AP MLD processes the uplink messages from the target non-AP MLD normally.

[0143] Using the method shown in this embodiment, the target non-AP MLD will not be aware of the seamless roaming process from link1 to link2. That is, the target non-AP MLD will not be aware of the seamless roaming from link1 supported by the first AP MLD to link2 of the second AP MLD. Without being aware of the seamless roaming process from link1 to link2, the target non-AP MLD conducts normal service transmission with the second AP MLD via link2, avoiding the interruption of communication between the target non-AP MLD and the AP MLD and ensuring the continuity of communication. In this embodiment, during the seamless roaming process from link1 to link2 of the target non-AP MLD, the target non-AP MLD and the first AP MLD continue to communicate normally through link3. Specifically, the first AP MLD communicates with the target non-AP MLD on link3 based on the association message shown above. This ensures the continuity of service transmission between the target non-AP MLD and the first AP MLD, and avoids the situation where the remaining links between the target non-AP MLD and the first AP MLD are disconnected due to the seamless roaming of the target non-AP MLD from link1 to link2. This ensures multi-link transmission between the target non-AP MLD and the AP MLD.

[0144] Step 310: The second AP MLD sends a first link activation feedback message to the AC.

[0145] If the second AP MLD successfully activates link2, it sends a first link activation feedback message to the AC indicating successful activation of link2. For example, this first link activation feedback message carries the identifier of the target non-AP MLD and at least one of the link2 ID and BSSID. Upon receiving this first link activation feedback message, the AC determines that the target non-AP MLD has successfully and seamlessly roamed from link1 to link2.

[0146] Step 311: AC sends a second shutdown instruction message to the first AP MLD.

[0147] When the AC determines that the first AP MLD needs to close link 3, the AC sends a second closure instruction message to the first AP MLD. This second closure instruction message instructs the first AP MLD to close link 3. Link 3 is a different link from link 1 among multiple links connecting the first AP MLD to the target non-AP MLD. For an explanation of the first AP MLD selecting link 3 from multiple links, please refer to the explanation of the first AP MLD selecting link 1 from multiple links; details will not be repeated here. The second closure instruction message carries the identifier of the target non-AP MLD, enabling the first AP MLD to determine and close the link used for communication with the target non-AP MLD based on this identifier. The second closure instruction message also carries at least one of the link 3's ID and link 3's BSSID, allowing the first AP MLD to identify link 3 as the specific link to be closed. This embodiment uses the AC sending a second closure instruction message to the first AP MLD as an example, and is not limited to this. For example, if the first AP MLD has AC functionality, it can directly close link 3. For example, the first AP MLD receives a second shutdown instruction message from the second AP MLD.

[0148] Step 312: The first AP MLD shuts down link3.

[0149] When the first AP MLD receives the second shutdown instruction message, the first AP MLD shuts down link3. For an explanation of how the first AP MLD shuts down link3, please refer to the explanation of how the first AP MLD shuts down link1 shown in step 306. Detailed explanation will not be repeated here.

[0150] Step 313: The first AP MLD sends a second link shutdown feedback message to the AC.

[0151] When the second AP MLD closes link 3, the first AP MLD sends a second link closure feedback message to the AC. This second link closure feedback message indicates that the first AP MLD has closed link 3. The second link closure feedback message carries at least one of the BSSID and identifier of link 3, and also carries the identifier of the target non-AP MLD. Based on this second link closure feedback message, the AC determines that link 3 between the first AP MLD and the target non-AP MLD has been closed by the first AP MLD.

[0152] Step 314: The AC sends a second link switching request to the second AP MLD.

[0153] Upon receiving a second link shutdown feedback message, the AC sends a second link handover request to the second AP MLD. This second link handover request instructs the target non-AP MLD to seamlessly roam from link 3 to link 4. To ensure successful roaming of the target non-AP MLD, this second link handover request instructs the second AP MLD to enable link 4. For example, the second link handover request carries the identifier of the target non-AP MLD, and also carries at least one of the link 4 ID and the link 4 BSSID.

[0154] This embodiment uses the example of the AC sending a second link switching request to the second AP MLD. In other examples, the first AP MLD can directly send the second link switching request to the second AP MLD.

[0155] Step 315: Enable link4 in the second AP MLD.

[0156] The description of enabling link4 of the second AP MLD shown in this embodiment can be found in the description of enabling link2 of the second AP MLD shown in step 309, and will not be repeated here.

[0157] Step 316: The second AP MLD sends a second link activation feedback message to the AC.

[0158] If the second AP MLD successfully activates link 4, it sends a second link activation feedback message to the AC indicating successful activation of link 4. For example, this second link activation feedback message carries the identifier of the target non-AP MLD and at least one of the link 4 ID and BSSID. Upon receiving this second link activation feedback message, the AC determines that the target non-AP MLD has successfully and seamlessly roamed from link 3 to link 4.

[0159] This embodiment uses the example of connecting two links between the first AP MLD and the target non-AP MLD, and connecting two links between the second AP MLD and the target non-AP MLD. In other examples, more links can be connected between the first AP MLD and the target non-AP MLD, and between the second AP MLD and the target non-AP MLD. The process of the target non-AP MLD seamlessly roaming from one link on the first AP MLD to another link on the second AP MLD can be described in the above description of the process of the target non-AP MLD seamlessly roaming from link1 on the first AP MLD to link2 on the second AP MLD. Specific details will not be repeated here.

[0160] Optionally, if the first AP MLD has closed link 1 with the target non-AP MLD and the second AP MLD has opened link 2 with the target non-AP MLD, thus ensuring the continuity of services between the target non-AP MLD and the second AP MLD, then the first AP MLD can uniformly close all remaining links with the target non-AP MLD except link 1, and the second AP MLD can uniformly open all remaining links with the target non-AP MLD except link 2, in order to further reduce the latency of the target non-AP MLD seamlessly roaming from the first AP MLD to the second AP MLD.

[0161] Using the method shown in this embodiment, when the first AP MLD and the target non-AP MLD are connected through multiple links, the target non-AP MLD can seamlessly roam from one link on the first AP MLD to one link on the second AP MLD without the need for the target non-AP MLD and the second AP MLD to re-initiate the probing process, authentication process, association process, key exchange, aggregation process, etc., so as to achieve a seamless roaming process with high throughput and low latency.

[0162] The roaming method shown in Figure 3 enables a target non-AP MLD to seamlessly roam from a link on a first AP MLD to a link on a second AP MLD without the target non-AP MLD's participation. Figure 7 is a flowchart of the steps of a second embodiment of the roaming method provided in this application. In the embodiment shown in Figure 7, the target non-AP MLD can participate in the process of seamlessly roaming from the first AP MLD to the second AP MLD.

[0163] Step 701: The AC sends the first configuration message to the first AP MLD.

[0164] Step 702: The AC sends a second configuration message to the second AP MLD.

[0165] Step 703: The first AP MLD sends the associated message corresponding to the target non-AP MLD to the AC.

[0166] Step 704: The AC sends the associated message corresponding to the target non-AP MLD to the second AP MLD.

[0167] Step 705: AC sends a first shutdown instruction message to the first AP MLD.

[0168] The processes shown in steps 701 to 705 of this embodiment are illustrated in Figure 3, which are shown in steps 301 to 305. The details will not be repeated here.

[0169] Step 706: The first AP MLD sends the first reconfiguration notification to the target non-AP MLD.

[0170] The first reconfiguration notification is used to notify the deletion of link1. The method by which the first AP MLD sends the first reconfiguration notification to the target non-AP MLD can be seen in the following optional methods:

[0171] Method 1

[0172] The first reconfiguration notification is specifically a first link reconfiguration notification, used to notify the deletion of link1. In this embodiment, the first AP MLD directly sends this first link reconfiguration notification to the target non-AP MLD. For example, the first AP MLD sends the first link reconfiguration notification to the target non-AP MLD through link1, or through link3. It can be understood that the first AP MLD in this embodiment can send the first link reconfiguration notification to the target non-AP MLD through any link between it and the target non-AP MLD. The first link reconfiguration notification in this embodiment can carry the identifier of the target non-AP MLD and a link deletion indication, and can also carry at least one of the ID of link1 and the BSSID. The link deletion indication is used to indicate the deletion of link1.

[0173] Method 2

[0174] In this method, the first AP MLD sends a first reconfiguration notification to the target non-AP MLD via the second AP MLD. Specifically, the first AP MLD sends a deletion instruction message to the second AP MLD. This deletion instruction message instructs the second AP MLD to send a first link reconfiguration notification to the target non-AP MLD. It can be understood that upon receiving the deletion instruction message, the second AP MLD sends the first link reconfiguration notification to the target non-AP MLD according to the deletion instruction message. For a description of the first link reconfiguration notification, please refer to Method 1; details will not be repeated here. The second AP MLD can send the first link reconfiguration notification to the target non-AP MLD via any link between it and the target non-AP MLD.

[0175] This embodiment does not limit the description of the first AP MLD sending the deletion instruction message to the second AP MLD. For example, the first AP MLD can directly send the deletion instruction message to the second AP MLD. Or, the first AP MLD sends the deletion instruction message to the AC, and the AC forwards the deletion instruction message to the second AP MLD.

[0176] Step 707: The target non-AP MLD sends a first link reconfiguration request to the first AP MLD.

[0177] In this embodiment, upon receiving a first reconfiguration notification, the target non-AP MLD determines, based on the notification, that it needs to seamlessly roam from link1 of the first AP MLD to link2 of the second AP MLD. The target non-AP MLD then sends a first link reconfiguration request to the first AP MLD, based on the notification. This request carries the identifier of the target non-AP MLD and at least one of the ID of link1 and the BSSID. This first link reconfiguration request is used to request the deletion of link1.

[0178] Step 708: The first AP MLD sends a first link reconfiguration response to the target non-AP MLD.

[0179] After receiving a first link reconfiguration request from a target non-AP MLD, the first AP MLD determines, based on at least one of the link1 ID and BSSID carried in the first link reconfiguration request, that the target non-AP MLD requests the deletion of link1. The first AP MLD then determines whether to agree to delete link1. Specifically, the first AP MLD assesses the link1's link status (e.g., signal quality, data transmission rate, packet loss rate) to determine if link1 can be deleted. For example, if the first AP MLD determines that the signal quality of link1 is low, then the first AP MLD will agree to delete link1.

[0180] If the first AP MLD determines that it agrees to delete link1, it sends a first link reconfiguration response to the target non-AP MLD. This first link reconfiguration response carries the identifier of the target non-AP MLD and at least one of the ID of link1 and its BSSID. This first link reconfiguration response is used to indicate to the target non-AP MLD that the first AP MLD agrees to delete link1. The target non-AP MLD deletes link1 based on the first link reconfiguration response. For details on deletion, please refer to the description of the first AP MLD closing link1; further details will not be elaborated here.

[0181] Through steps 706 to 708 shown in this embodiment, the purpose of the first AP MLD instructing the target non-AP MLD to delete link1 is achieved. It should be noted that the description of the method by which the first AP MLD instructs the target non-AP MLD to delete link1 in this embodiment is an optional example and is not limited, as long as the first AP MLD can successfully instruct the target non-AP MLD to delete link1.

[0182] Step 709: The first AP MLD shuts down link1.

[0183] For an explanation of the execution process of step 709 shown in this embodiment, please refer to step 306 in Figure 3, which will not be elaborated upon here. This embodiment does not limit the execution sequence of step 709 and steps 706 to 708.

[0184] Optionally, if the first AP MLD shuts down link1, it can return a first link shutdown feedback message to the AC. For an explanation of the first link shutdown feedback message, please refer to step 307 in Figure 3, which will not be elaborated further.

[0185] Step 710: AC sends a first activation instruction message to the second AP MLD.

[0186] The first activation indication message is used to instruct the second AP MLD to activate link2. For example, the first activation indication message carries the identifier of the target non-AP MLD, and also carries at least one of the ID of link2 and BSSID. This embodiment takes the AC sending the first activation indication message to the second AP MLD as an example. In other examples, the first AP MLD can send the first activation indication message to the second AP MLD.

[0187] Step 711: Enable link2 in the second AP MLD.

[0188] For an explanation of the execution process of step 711 shown in this embodiment, please refer to step 309 in Figure 3, which will not be elaborated further.

[0189] Optionally, if the second AP MLD enables link2, it can return a first link enable feedback message to the AC. For an explanation of the first link enable feedback message, please refer to step 310 in Figure 3, which will not be elaborated further.

[0190] Step 712: The second AP MLD sends a second link reconfiguration notification to the target non-AP MLD.

[0191] In this embodiment, after the second AP MLD enables link2, it sends a second link reconfiguration notification to the target non-AP MLD. The second link reconfiguration notification is used to notify the target non-AP MLD to add link2. The second link reconfiguration notification carries the identifier of the target non-AP MLD, and at least one of the identifier of link2 and BSSID. The second AP MLD can send this second link reconfiguration notification through any link between the second AP MLD and the target non-AP MLD.

[0192] This embodiment uses the example of a second AP MLD sending a second link reconfiguration notification to a target non-AP MLD, but it is not limited to this example. For instance, if the first AP MLD successfully closes link 1 of the target non-AP MLD, the first AP MLD can send the second link reconfiguration notification to the target non-AP MLD. The first AP MLD can send this second link reconfiguration notification through any link between the first AP MLD and the target non-AP MLD. For example, the first AP MLD can send the second link reconfiguration notification through link 3.

[0193] Step 713: The target non-AP MLD sends a second link reconfiguration request to the second AP MLD.

[0194] In this embodiment, when the target non-AP MLD receives the second link reconfiguration notification, the target non-AP MLD sends a second link reconfiguration request to the second AP MLD. This second link reconfiguration request is used to request the addition of link2. The second link reconfiguration request carries the identifier of the target non-AP MLD, and also carries at least one of the link2 ID and BSSID.

[0195] Optionally, if the target non-AP MLD receives a second link reconfiguration notification from the first AP MLD, the target non-AP MLD sends a second link reconfiguration request to the first AP MLD. For example, the target non-AP MLD sends a second link reconfiguration request to the first AP MLD via link3.

[0196] Step 714: The second AP MLD sends a second link reconfiguration response to the target non-AP MLD.

[0197] After receiving the second link reconfiguration request, the second AP MLD determines, based on at least one of the link2 ID and BSSID carried in the request, whether the target non-AP MLD requests to add link2. The second AP MLD then determines whether to agree to add link2. Specifically, the second AP MLD assesses the link status of link2 (e.g., signal quality, data transmission rate, packet loss rate) and whether link1 can be added. If the second AP MLD determines that the signal quality of link2 is higher, then it agrees to add link2.

[0198] If the second AP MLD determines that it agrees to add link2, it sends a second link reconfiguration response to the target non-AP MLD. This second link reconfiguration response carries the identifier of the target non-AP MLD and at least one of the following: the link2 ID and the BSSID. This second link reconfiguration response is used to indicate to the target non-AP MLD that the second AP MLD agrees to add link2. The target non-AP MLD adds link2 based on the second link reconfiguration response.

[0199] Optionally, if the target non-AP MLD sends a second link reconfiguration request to the first AP MLD via link3, the first AP MLD sends the second link reconfiguration response to the target non-AP MLD via link3.

[0200] When link2 is added to the target non-AP MLD, the target non-AP MLD can seamlessly roam from link1 of the first AP MLD to link2 of the second AP MLD.

[0201] The steps 712 to 714 shown in this embodiment, which illustrate the method of adding link2 to the target non-AP MLD, are optional examples and are not limited.

[0202] The above describes the process of seamlessly roaming a target non-AP MLD from link 1 of the first AP MLD to link 2 of the second AP MLD. The following steps illustrate the process of seamlessly roaming a target non-AP MLD from link 3 of the first AP MLD to link 4 of the second AP MLD:

[0203] Step 715: AC sends a second shutdown instruction message to the first AP MLD.

[0204] For an explanation of the execution process of step 715 shown in this embodiment, please refer to step 311 in Figure 3, which will not be elaborated further.

[0205] Step 716: The first AP MLD sends a second configuration notification to the target non-AP MLD.

[0206] The second reconfiguration notification is used to notify the deletion of link3. The explanation of how the first AP MLD sends the second reconfiguration notification to the target non-AP MLD can be found in step 706, which describes how the first AP MLD sends the first reconfiguration notification to the target non-AP MLD; details will not be repeated here. The second link reconfiguration notification shown in this embodiment may carry the identifier of the target non-AP MLD and a link deletion indication. Furthermore, the second link reconfiguration notification may also carry at least one of the link3 ID and BSSID. The link deletion indication is used to instruct the deletion of link3.

[0207] Step 717: The target non-AP MLD sends a third link reconfiguration request to the first AP MLD.

[0208] In this embodiment, when the target non-AP MLD receives the second reconfiguration notification, it determines that it needs to seamlessly roam from link 3 of the first AP MLD to link 4 of the second AP MLD based on the notification. The target non-AP MLD then sends a third link reconfiguration request to the first AP MLD based on the second reconfiguration notification. For a description of the third link reconfiguration request, please refer to the description of the first link reconfiguration request shown in step 707; details will not be repeated here. It is understood that the third link reconfiguration request carries the identifier of the target non-AP MLD and at least one of the link 3 ID and BSSID. This third link reconfiguration request is used to request the deletion of link 3.

[0209] Step 718: The first AP MLD sends a third link reconfiguration response to the target non-AP MLD.

[0210] After receiving the third link reconfiguration request from the target non-AP MLD, the first AP MLD determines that the target non-AP MLD requests to delete link3 based on at least one of the link3 ID and BSSID carried in the third link reconfiguration request. Then, the first AP MLD sends a third link reconfiguration response to the target non-AP MLD to instruct the target non-AP MLD to delete link3. For a description of the execution process of step 718 shown in this embodiment, please refer to step 708, which will not be repeated here.

[0211] Step 719: The first AP MLD shuts down link3.

[0212] For an explanation of the execution process of step 719 shown in this embodiment, please refer to step 709; details will not be repeated here.

[0213] Optionally, if the first AP MLD shuts down link3, the first AP MLD sends a second link shutdown feedback message to the AC. For an explanation of the second link shutdown feedback message, please refer to step 313 in Figure 3, which will not be elaborated further.

[0214] Step 720: AC sends a second activation instruction message to the second AP MLD.

[0215] The second activation indication message is used to instruct the second AP MLD to activate link4. For example, the second activation indication message carries the identifier of the target non-AP MLD, and also carries at least one of the ID of link4 and the BSSID. The description of the execution process of step 720 shown in this embodiment can be found in step 710, and will not be repeated here.

[0216] Step 721: Enable link4 in the second AP MLD.

[0217] For an explanation of the execution process of step 721 shown in this embodiment, please refer to the explanation of enabling link2 of the second AP MLD shown in step 711, which will not be repeated here.

[0218] Optionally, if the second AP MLD successfully enables link4, the second AP MLD sends a second link enable feedback message to the AC to indicate that link4 has been successfully enabled. For an explanation of the second link enable feedback message, please refer to step 316 in Figure 3, which will not be elaborated further.

[0219] Step 722: The second AP MLD sends a fourth link reconfiguration notification to the target non-AP MLD.

[0220] In this embodiment, after the second AP MLD enables link4, it sends a fourth link reconfiguration notification to the target non-AP MLD. The fourth link reconfiguration notification is used to notify the target non-AP MLD to add link4. The fourth link reconfiguration notification carries the identifier of the target non-AP MLD, and at least one of the identifier of link4 and BSSID. For a detailed explanation of the specific execution process of step 722 in this embodiment, please refer to step 712; further details will not be elaborated here.

[0221] Step 723: The target non-AP MLD sends a fourth link reconfiguration request to the second AP MLD.

[0222] In this embodiment, when the target non-AP MLD receives the fourth link reconfiguration notification, the target non-AP MLD sends a fourth link reconfiguration request to the second AP MLD. This fourth link reconfiguration request is used to request the addition of link4. The fourth link reconfiguration request carries the identifier of the target non-AP MLD, and carries at least one of the link4 ID and BSSID. For a detailed explanation of the process, please refer to step 713, which will not be elaborated further.

[0223] Step 724: The second AP MLD sends a fourth link reconfiguration response to the target non-AP MLD.

[0224] The second AP MLD determines that the target non-AP MLD requests to add link4 based on at least one of the link4 ID and BSSID carried in the fourth link reconfiguration request. Then, the second AP MLD sends a fourth link reconfiguration response to the target non-AP MLD to indicate that it agrees to add link4. For a detailed explanation of the process, please refer to step 714, which will not be elaborated further.

[0225] This embodiment uses the example of connecting two links between the first AP MLD and the target non-AP MLD, and connecting two links between the second AP MLD and the target non-AP MLD. In other examples, more links can be connected between the first AP MLD and the target non-AP MLD, and between the second AP MLD and the target non-AP MLD. The process of the target non-AP MLD seamlessly roaming from one link on the first AP MLD to another link on the second AP MLD can be described in the above description of the process of the target non-AP MLD seamlessly roaming from link1 on the first AP MLD to link2 on the second AP MLD. Specific details will not be repeated here.

[0226] Optionally, if the first AP MLD has closed link 1 with the target non-AP MLD and the second AP MLD has opened link 2 with the target non-AP MLD, thus ensuring the continuity of services between the target non-AP MLD and the second AP MLD, then the first AP MLD can uniformly close all remaining links with the target non-AP MLD except link 1, and the second AP MLD can uniformly open all remaining links with the target non-AP MLD except link 2, in order to further reduce the latency of the target non-AP MLD seamlessly roaming from the first AP MLD to the second AP MLD.

[0227] Figure 8 is a flowchart of the steps of the third embodiment of the roaming method provided in this application.

[0228] Step 801: The AC sends the first configuration message to the first AP MLD.

[0229] Step 802: The AC sends a second configuration message to the second AP MLD.

[0230] Step 803: The first AP MLD sends the associated message corresponding to the target non-AP MLD to the AC.

[0231] Step 804: The AC sends the associated message corresponding to the target non-AP MLD to the second AP MLD.

[0232] Step 805: AC sends a first shutdown instruction message to the first AP MLD.

[0233] For an explanation of the execution process of steps 801 to 805 shown in this embodiment, please refer to steps 701 to 705 in Figure 7, which will not be described in detail here.

[0234] Step 806: The first AP MLD shuts down link1.

[0235] When the first AP MLD receives the first shutdown instruction message, it shuts down link1. For an explanation of the process of shutting down link1, please refer to step 709 in Figure 7, which will not be elaborated here.

[0236] Optionally, if the first AP MLD shuts down link1, it can return a first link shutdown feedback message to the AC. For an explanation of the first link shutdown feedback message, please refer to step 307 in Figure 3, which will not be elaborated further.

[0237] Step 807: The first AP MLD sends a first shutdown instruction frame to the target non-AP MLD.

[0238] The first shutdown indication frame can be a beacon frame or a probe response frame, etc. The first shutdown indication frame is used to indicate that the first AP MLD has shut down link1. Specifically, the first shutdown indication frame carries at least one of the identifiers and BSSIDs of the currently configured links for the target non-AP MLD by the first AP MLD. For example, before executing step 806, the first AP MLD configures at least one of the identifiers and BSSIDs of link1 for the target non-AP MLD, and also configures at least one of the identifiers and BSSIDs of link3. After executing step 806, the first AP MLD has shut down link1. Then, the first AP MLD configures at least one of the identifiers and BSSIDs of link3 for the target non-AP MLD. Therefore, the first shutdown indication frame carries the identifier of the target non-AP MLD, and also carries at least one of the identifiers and BSSIDs of link3. When the target non-AP MLD receives the first shutdown indication frame, it determines that link3 is in the open state, but link1 is in the closed state, based on the identifiers and BSSIDs of link3 carried in the first shutdown indication frame. The first AP MLD can broadcast or unicast the first shutdown indication frame.

[0239] Step 808: The target non-AP MLD sends a first link reconfiguration request to the first AP MLD.

[0240] Step 809: The first AP MLD sends a first link reconfiguration response to the target non-AP MLD.

[0241] For an explanation of the execution process of steps 808 to 809 shown in this embodiment, please refer to steps 707 to 708 in Figure 7, which will not be described in detail here.

[0242] Step 810: AC sends a first activation instruction message to the second AP MLD.

[0243] Step 811: Enable link2 in the second AP MLD.

[0244] Optionally, if the second AP MLD enables link2, it can return a first link enable feedback message to the AC. For an explanation of the first link enable feedback message, please refer to step 310 in Figure 3, which will not be elaborated further.

[0245] For an explanation of the execution process of steps 808 to 811 shown in this embodiment, please refer to steps 708 to 711 in Figure 7, which will not be described in detail here.

[0246] Step 812: The second AP MLD sends the first enable instruction frame to the target non-AP MLD.

[0247] The first activation indication frame can be a Beacon or Probe Response, etc. The first activation indication frame is used to indicate which link has been activated by the second AP MLD. Specifically, the first activation indication frame carries at least one of the following: the identifier of the currently configured link for the target non-AP MLD by the second AP MLD, and the BSSID. After executing step 811, if the second AP MLD has activated link2, then the second AP MLD configures at least one of the identifier of link2 and the BSSID for the target non-AP MLD. Therefore, the first activation indication frame carries the identifier of the target non-AP MLD, as well as the identifier of link2 and at least one of the BSSID. When the target non-AP MLD receives the first activation indication frame, it determines that link2 is in the activated state based on the identifier of link2 and the BSSID carried in the first activation indication frame.

[0248] Step 813: The target non-AP MLD sends a second link reconfiguration request to the second AP MLD.

[0249] Step 814: The second AP MLD sends a second link reconfiguration response to the target non-AP MLD.

[0250] Step 815: AC sends a second shutdown instruction message to the first AP MLD.

[0251] For an explanation of the execution process of steps 813 to 815 shown in this embodiment, please refer to the explanation of the execution process of steps 713 to 715 corresponding to Figure 7, which will not be repeated here.

[0252] Step 816: The first AP MLD shuts down link3.

[0253] Optionally, if the first AP MLD shuts down link3, the first AP MLD sends a second link shutdown feedback message to the AC. For an explanation of the second link shutdown feedback message, please refer to step 313 in Figure 3, which will not be elaborated further.

[0254] For an explanation of the execution process of step 816 shown in this embodiment, please refer to step 719 in Figure 7, which will not be elaborated further.

[0255] Step 817: The first AP MLD sends a second shutdown instruction frame to the target non-AP MLD.

[0256] The second shutdown indication frame is used to indicate that the first AP MLD has shut down link3. For an explanation of the second shutdown indication frame, please refer to the explanation of the first shutdown indication frame shown in step 807. Detailed explanation will not be repeated here.

[0257] Step 818: The target non-AP MLD sends a third link reconfiguration request to the first AP MLD.

[0258] Step 819: The first AP MLD sends a third link reconfiguration response to the target non-AP MLD.

[0259] As shown in steps 818 to 819 of this embodiment, please refer to steps 717 to 718 in Figure 7, which will not be described in detail here.

[0260] Step 820: AC sends a second activation instruction message to the second AP MLD.

[0261] Step 821: Enable link4 in the second AP MLD.

[0262] Optionally, if the second AP MLD successfully enables link4, the second AP MLD sends a second link enable feedback message to the AC to indicate that link4 has been successfully enabled. For an explanation of the second link enable feedback message, please refer to step 316 in Figure 3, which will not be elaborated further.

[0263] For an explanation of the execution process of steps 820 to 821 shown in this embodiment, please refer to steps 720 to 721 in Figure 7. Detailed explanations will not be repeated here.

[0264] Step 822: The second AP MLD sends a second enable instruction frame to the target non-AP MLD.

[0265] The second activation indication frame can be a Beacon or Probe Response, etc. The second activation indication frame is used to indicate that the second AP MLD has activated a link. Specifically, the second activation indication frame carries at least one of the identifier of the currently configured link and the BSSID for the target non-AP MLD. After executing step 811, the second AP MLD has activated link 2. After executing step 821, the second AP MLD has activated link 4. Therefore, the second activation indication frame carries the identifier of the target non-AP MLD, and also carries at least one of the identifier of link 2 and the BSSID. The second activation indication frame also carries at least one of the identifier of link 4 and the BSSID. When the target non-AP MLD receives the second activation indication frame, it determines that link 2 is in the activated state based on the identifier of link 2 and the BSSID carried in the second activation indication frame, and also determines that link 4 is in the activated state based on the identifier of link 4 and the BSSID carried in the second activation indication frame.

[0266] Step 823: The target non-AP MLD sends a fourth link reconfiguration request to the second AP MLD.

[0267] Step 824: The second AP MLD sends a fourth link reconfiguration response to the target non-AP MLD.

[0268] For an explanation of the execution process of steps 820 to 824 shown in this embodiment, please refer to steps 720 to 724 in Figure 7, which will not be described in detail here.

[0269] Figure 9 is a flowchart of the steps of the fourth embodiment of the roaming method provided in this application.

[0270] Step 901: The AC sends the first configuration message to the first AP MLD.

[0271] Step 902: The AC sends a second configuration message to the second AP MLD.

[0272] Step 903: The first AP MLD sends the associated message corresponding to the target non-AP MLD to the AC.

[0273] Step 904: The AC sends the associated message corresponding to the target non-AP MLD to the second AP MLD.

[0274] Step 905: AC sends a first shutdown instruction message to the first AP MLD.

[0275] Step 906: The first AP MLD sends the first reconfiguration notification to the target non-AP MLD.

[0276] Step 907: The target non-AP MLD sends a first link reconfiguration request to the first AP MLD.

[0277] Step 908: The first AP MLD sends a first link reconfiguration response to the target non-AP MLD.

[0278] Step 909: The first AP MLD shuts down link1.

[0279] Optionally, if the first AP MLD shuts down link1, it can return a first link shutdown feedback message to the AC. For an explanation of the first link shutdown feedback message, please refer to step 307 in Figure 3, which will not be elaborated further.

[0280] For an explanation of the execution process of steps 901 to 909 shown in this embodiment, please refer to steps 701 to 709 in Figure 7, which will not be described in detail here.

[0281] Step 910: The first AP MLD sends a fifth link reconfiguration notification to the second AP MLD.

[0282] The fifth link reconfiguration notification is used to notify the second AP MLD to enable link2. The fifth link reconfiguration notification carries the identifier of the target non-AP MLD and carries at least one of the identifier of link2 and BSSID.

[0283] This embodiment uses the example of the first AP MLD sending a fifth link reconfiguration notification to the second AP MLD. In other examples, the AC can send the fifth link reconfiguration notification to the second AP MLD.

[0284] Step 911: Enable link2 in the second AP MLD.

[0285] When the second AP MLD receives the reconfiguration notification for the fifth link, it enables link2. For instructions on enabling link2, please refer to step 711 in Figure 7, which will not be elaborated here.

[0286] Optionally, if the second AP MLD enables link2, it can return a first link enable feedback message to the AC. For an explanation of the first link enable feedback message, please refer to step 310 in Figure 3, which will not be elaborated further.

[0287] Step 912: The second AP MLD sends a second link reconfiguration notification to the target non-AP MLD.

[0288] Step 913: The target non-AP MLD sends a second link reconfiguration request to the second AP MLD.

[0289] Step 914: The second AP MLD sends a second link reconfiguration response to the target non-AP MLD.

[0290] Step 915: AC sends a second shutdown instruction message to the first AP MLD.

[0291] Step 916: The first AP MLD sends a second configuration notification to the target non-AP MLD.

[0292] Step 917: The target non-AP MLD sends a third link reconfiguration request to the first AP MLD.

[0293] Step 918: The first AP MLD sends a third link reconfiguration response to the target non-AP MLD.

[0294] Step 919: The first AP MLD shuts down link3.

[0295] Optionally, if the first AP MLD shuts down link3, the first AP MLD sends a second link shutdown feedback message to the AC. For an explanation of the second link shutdown feedback message, please refer to step 313 in Figure 3, which will not be elaborated further.

[0296] For an explanation of the execution process of steps 912 to 919 shown in this embodiment, please refer to steps 712 to 719 in Figure 7. Detailed explanations will not be repeated here.

[0297] Step 920: The first AP MLD sends a sixth link reconfiguration notification to the second AP MLD.

[0298] The sixth link reconfiguration notification is used to notify the second AP MLD to enable link4. The sixth link reconfiguration notification carries the identifier of the target non-AP MLD and carries at least one of the identifier of link4 and BSSID.

[0299] This embodiment uses the example of the first AP MLD sending a sixth link reconfiguration notification to the second AP MLD. In other examples, the AC can send the sixth link reconfiguration notification to the second AP MLD.

[0300] Step 921: Enable link4 in the second AP MLD.

[0301] Optionally, if the second AP MLD successfully enables link4, the second AP MLD sends a second link enable feedback message to the AC to indicate that link4 has been successfully enabled. For an explanation of the second link enable feedback message, please refer to step 316 in Figure 3, which will not be elaborated further.

[0302] Step 922: The second AP MLD sends a fourth link reconfiguration notification to the target non-AP MLD.

[0303] Step 923: The target non-AP MLD sends a fourth link reconfiguration request to the second AP MLD.

[0304] Step 924: The second AP MLD sends a fourth link reconfiguration response to the target non-AP MLD.

[0305] For an explanation of the execution process of steps 921 to 924 shown in this embodiment, please refer to steps 721 to 724 in Figure 7. Detailed explanations will not be repeated here.

[0306] It should be clarified that the above description of each message type is only an optional example and is not limited. The messages shown above can also adopt private protocols or message types defined by subsequent Wi-Fi protocols to enable a single AP MLD to support multiple links and realize various message types for link deletion or activation in scenarios with seamless roaming.

[0307] Optionally, when the target non-AP MLD seamlessly roams from the first AP MLD to the second AP MLD, different links can perform seamless roaming through different method embodiments shown in Figures 3, 7, 8 and 9.

[0308] In the above method embodiments, the network structure is Example 1, where the MAC address of the first AP MLD is the same as the MAC address of the second AP MLD, the BSSID and ID of link 1 of the first AP MLD are the same as the BSSID and ID of link 2 of the second AP MLD, and the BSSID and ID of link 3 of the first AP MLD are the same as the BSSID and ID of link 4 of the second AP MLD. In other embodiments, there may be other examples, such as Example 2, where the MAC address of the first AP MLD is the same as the MAC address of the second AP MLD, the BSSID and ID of link 1 of the first AP MLD are the same as the BSSID and ID of link 2 of the second AP MLD, the BSSID of link 3 of the first AP MLD is different from the BSSID of link 4 of the second AP MLD, and the ID of link 3 of the first AP MLD is different from the ID of link 4 of the second AP MLD. For example, in Example 3, the MAC address of the first AP MLD is the same as that of the second AP MLD. However, the BSSID of link 1 of the first AP MLD is different from the BSSID of link 2 of the second AP MLD, the ID of link 1 of the first AP MLD is different from the ID of link 2 of the second AP MLD, the BSSID of link 3 of the first AP MLD is different from the BSSID of link 4 of the second AP MLD, and the ID of link 3 of the first AP MLD is different from the ID of link 4 of the second AP MLD. The network structure can also be a variation of the above examples, or the network structure can include a combination of at least two of the above examples. For example, some AP MLDs use the structure shown in Example 1 above, and some AP MLDs use the structure shown in Example 2 above, etc. The seamless roaming process performed in each example is shown in any of the above method embodiments, and will not be elaborated further.

[0309] The AP MLD and non-AP MLD involved in the embodiments of this application can be collectively referred to as WLAN devices. In specific implementation, the WLAN device can adopt the composition structure shown in Figure 10, wherein Figure 10 is a first structural example diagram of the wireless local area network device provided in this application.

[0310] The WLAN device 1000 specifically includes a processor 1001 and a transceiver 1003. Optionally, the WLAN device 1000 also includes a memory 1002. The processor 1001 is connected to the memory 1002 and the transceiver 1003 via a system bus 1011. The processor 1001 can access the memory 1002 via the system bus 1011; for example, the processor 1001 can perform data read / write operations or code execution in the memory 1002 via the system bus 1011. The system bus 1011 can be, for example, a quick path interconnect (QPI) or an ultra path interconnect (UPI). The system bus 1011 is divided into an address bus, a data bus, and a control bus. The main function of the processor 1001 is to interpret the instructions (or code) of the computer program and process the data in the computer software. The instructions of the computer program and the data in the computer software can be stored in the memory 1002. The processor 1001 may include one or more chips, or one or more integrated circuits. For example, the processor may include one or more of the following: neural processing unit (NPU), optical digital signal processor (oDSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), system-on-chip (SoC), central processing unit (CPU), microcontroller unit (MCU), programmable logic device (PLD), network interface card chip, storage interface chip, or other integrated chip, etc. Specific details are omitted. The transceiver 1003 may be a module, circuit, transceiver device, or any device capable of communication. The memory 1002 is used to store instructions. These instructions may be computer programs.The memory 1002 can be a read-only memory (ROM) or other type of static storage device capable of storing static information and / or instructions; it can also be a random access memory (RAM) or other type of dynamic storage device capable of storing information and / or instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, etc., without limitation. It should be noted that the memory 1002 can exist independently of the processor 1001 or can be integrated with the processor 1001. The memory 1002 can be used to store instructions, program code, or some data, etc. The memory 1002 can be located inside or outside the WLAN device 1000, without limitation. The processor 1001 is configured to execute instructions stored in the memory 1002 to implement the method provided in this application embodiment, which is implemented by a WLAN device.

[0311] Figure 11 is a second structural example of the wireless local area network (WLAN) device provided in this application. Specifically, the WLAN device 1100 includes a transmitting module 1101, a processing module 1102, and a receiving module 1103. The transmitting module 1101 can also be referred to as a transmitter, transmitting unit, or transmitting device. The receiving module 1103 can also be referred to as a receiver, receiving unit, or receiving device. The processing module 1102 is used to implement corresponding processing functions. The transmitting module 1101 and the receiving module 1103 can also be referred to as a communication interface or communication unit.

[0312] Optionally, the WLAN device 1100 also includes a storage unit, which can be used to store instructions and / or data. The processing module 1102 can read the instructions and / or data in the storage unit to perform corresponding processing control actions.

[0313] For example, WLAN device 1100 can be the first AP MLD shown in the above embodiment. In the above method embodiment, the sending module 1101 is used to execute the sending-related steps implemented by the first AP MLD, the processing module 1102 is used to execute the processing-related steps implemented by the first AP MLD, and the receiving module 1103 is used to execute the receiving-related steps implemented by the first AP MLD.

[0314] For example, the WLAN device 1100 can be the second AP MLD shown in the above embodiment. In the above method embodiment, the sending module 1101 is used to execute the sending-related steps implemented by the second AP MLD, the processing module 1102 is used to execute the processing-related steps implemented by the second AP MLD, and the receiving module 1103 is used to execute the receiving-related steps implemented by the second AP MLD.

[0315] For example, if the WLAN device 1100 can be the target non-AP MLD shown in the above embodiment, then in the above method embodiment, the transmitting module 1101 is used to perform the transmitting-related steps implemented by the target non-AP MLD, the processing module 1102 is used to perform the processing-related steps implemented by the target non-AP MLD, and the receiving module 1103 is used to perform the receiving-related steps implemented by the target non-AP MLD.

[0316] It should be understood that the specific process of each module performing the above-mentioned steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0317] Figure 12 is a schematic diagram of an embodiment of the chip provided in this application. The chip 1200 (or may also be referred to as a processing system) includes logic circuitry 1210 and a communication interface (input / output interface) 1220.

[0318] The logic circuit 1210 can be a processing circuit in the chip 1200. The logic circuit 1210 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip 1200 to implement the methods and functions of the embodiments of this application. The communication interface 1220 can be an input / output circuit in the chip 1200, outputting processed information from the chip 1200, or inputting data or signaling information to be processed into the chip 1200 for processing.

[0319] Optionally, the logic circuit 1210 may be implemented by one or more processors, including the one or more processors or the processing portion of the one or more processors.

[0320] Optionally, the communication interface 1220 may include transceiver circuitry, transceiver, input / output circuitry, or a communication interface.

[0321] As one approach, the chip 1200 is used to implement the operations performed by the first AP MLD, the second AP MLD, or the target non-AP MLD in the various method embodiments described above.

[0322] Specifically, the logic circuit 1210 is used to implement the processing-related operations performed by the first AP MLD, the second AP MLD, or the target non-AP MLD in the above method embodiment; the communication interface 1220 is used to implement the sending and / or receiving-related operations performed by the first AP MLD, the second AP MLD, or the target non-AP MLD in the above method embodiment.

[0323] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the first AP MLD, the second AP MLD, or the target non-AP MLD in the above-described method embodiments.

[0324] For example, when the computer program is executed by a computer, it enables the computer to implement the methods performed by the first AP MLD, the second AP MLD, or the target non-AP MLD in the various embodiments of the above methods.

[0325] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods described above, executed by a first AP MLD, a second AP MLD, or a target non-AP MLD.

[0326] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0327] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A roaming method, characterized in that, The roaming method is applied to a communication network, which includes L access point multi-link devices (AP MLDs), where L is any integer greater than or equal to 2. The first AP MLD supports multiple links, including a first link, and the second AP MLD supports multiple links, including a second link. The method includes: The first AP MLD sends an association message to the second AP MLD. The association message corresponds to a terminal device and is used for the first AP MLD to communicate with the terminal device on the first link. The first AP MLD shuts down the first link, and the associated message is also used for the second AP MLD to communicate with the terminal device on the second link.

2. The method according to claim 1, characterized in that, The first AP MLD supports multiple links, including a third link. After the first AP MLD sends an association message to the second AP MLD, the method further includes: The first AP MLD communicates with the terminal device on the third link based on the associated message.

3. The method according to claim 2, characterized in that, The second AP MLD also supports a fourth link among multiple links. After the first AP MLD sends an association message to the second AP MLD, the method further includes: The first AP MLD shuts down the third link.

4. The method according to any one of claims 1 to 3, characterized in that, Before the first AP MLD shuts down the first link, the method further includes: The first AP MLD obtains a first configuration message, which carries the target media access control layer MAC address, the target basic service set identifier (BSSID), and the target identifier. The MAC address of the second AP MLD is the target MAC address, the BSSID of the second link is the target BSSID, and the identifier of the second link is the target identifier. According to the first configuration message, the first AP MLD configures the MAC address of the first AP MLD to the target MAC address, configures the BSSID of the first link to the target BSSID, and configures the identifier of the first link to the target identifier.

5. The method according to claim 4, characterized in that, The first AP MLD receives the first configuration message, which includes: The first AP MLD receives the first configuration message from the master control device, wherein the master control device is connected to both the first AP MLD and the second AP MLD. or, The first AP MLD receives the first configuration message from the second AP MLD; or, The first AP MLD generates the first configuration message locally.

6. The method according to claim 4, characterized in that, After the first AP MLD obtains the first configuration message, the method further includes: The first AP MLD sends a second configuration message to the second AP MLD. The second configuration message carries the target MAC address, the target BSSID, the target identifier, and the identifier of the second AP MLD.

7. The method according to any one of claims 4 to 6, characterized in that, The first configuration message also carries at least one of the following: encryption key, target service set identifier (SSID), password, encryption method, channel bandwidth, and wireless standard; Wherein, the terminal device uses the encryption key to access the first link, the SSID of the wireless network to which the first link belongs is the target SSID, the terminal device authenticates with the first AP MLD based on the password, the encryption method is the encryption method for data transmission on the first link, the channel bandwidth is the channel bandwidth of the first link, and the wireless standard is the wireless standard supported by the first link.

8. The method according to any one of claims 1 to 7, characterized in that, The first AP MLD shuts down the first link by: The first AP MLD deletes the first link; or, The first link of the first AP MLD is not used to send downlink messages to the terminal device, and the first AP MLD discards uplink messages received from the terminal device via the first link. or, The first link of the first AP MLD is not used to send downlink messages to any terminal device, and the first AP MLD discards uplink messages received via the first link from any terminal device.

9. The method according to any one of claims 1 to 8, characterized in that, Before the first AP MLD shuts down the first link, the method further includes: The first AP MLD receives a shutdown instruction message, which instructs the first AP MLD to shut down the first link. The shutdown instruction message carries at least one of the following: the BSSID of the first link, the identifier of the first link, and the identifier of the terminal device.

10. The method according to any one of claims 1 to 9, characterized in that, After the first AP MLD shuts down the first link, the method further includes: The first AP MLD sends a link switching request to the second AP MLD. The link switching request is used to instruct the terminal device to roam from the first link to the second link. The link switching request is used to request the second AP MLD to activate the second link. The link switching request carries at least one of the BSSID of the first link and the identifier of the first link. The link switching request also carries the identifier of the terminal device.

11. The method according to any one of claims 1 to 9, characterized in that, After the first AP MLD shuts down the first link, the method further includes: The first AP MLD sends a link shutdown feedback message to the master control device. The link shutdown feedback message is used to indicate that the first AP MLD has shut down the first link. The link shutdown feedback message carries at least one of the BSSID of the first link and the identifier of the first link. The link shutdown feedback message also carries the identifier of the terminal device.

12. The method according to any one of claims 1 to 9, characterized in that, After the first AP MLD sends an association message to the second AP MLD, the method further includes: The first AP MLD instructs the terminal device to delete the first link; The first AP MLD instructs the terminal device to add the second link.

13. The method according to any one of claims 1 to 9, characterized in that, After the first AP MLD sends an association message to the second AP MLD, the method further includes: The first AP MLD sends a reconfiguration notification, which is used to notify the deletion of the first link; The first AP MLD receives a first link reconfiguration request from the terminal device, the first link reconfiguration request being used to request the deletion of the first link; The first AP MLD sends a link reconfiguration response to the terminal device, the link reconfiguration response being used to indicate the deletion of the first link.

14. The method according to claim 13, characterized in that, The reconfiguration notification is a first link reconfiguration notification, and the first AP MLD sends the reconfiguration notification including: The first AP MLD sends a first link reconfiguration notification to the terminal device. The first link reconfiguration notification carries the identifier of the terminal device and a link deletion indication. The first link reconfiguration notification also carries at least one of the identifier of the first link and the BSSID. The link deletion indication is used to indicate the deletion of the first link.

15. The method according to claim 13, characterized in that, The reconfiguration notification is a deletion indication message, and the first AP MLD sends the reconfiguration notification including: The first AP MLD sends the deletion instruction message to the second AP MLD. The deletion instruction message is used to instruct the second AP MLD to send a first link reconfiguration notification to the terminal device. The first link reconfiguration notification carries the identifier of the terminal device and a link deletion instruction. The first link reconfiguration notification carries at least one of the identifier of the first link and the BSSID. The link deletion instruction is used to instruct the deletion of the first link.

16. The method according to any one of claims 1 to 9, characterized in that, After the first AP MLD shuts down the first link, the method further includes: The first AP MLD sends a shutdown indication frame to the terminal device. The shutdown indication frame is a beacon frame or a probe response frame. The shutdown indication frame is used to indicate that the first AP MLD has shut down the first link. The first AP MLD receives a first link reconfiguration request from the terminal device, the first link reconfiguration request being used to request the deletion of the first link; The first AP MLD sends a link reconfiguration response to the terminal device, the link reconfiguration response being used to indicate the deletion of the first link.

17. The method according to any one of claims 13 to 16, characterized in that, After the first AP MLD sends an association message to the second AP MLD, the method further includes: The first AP MLD sends a second link reconfiguration notification to the terminal device. The second link reconfiguration notification is used to notify the terminal device to add the second link. The second link reconfiguration notification carries the identifier of the terminal device and at least one of the identifier of the second link and the BSSID.

18. The method according to any one of claims 13 to 17, characterized in that, After the first AP MLD sends an association message to the second AP MLD, the method further includes: The first AP MLD sends a link reconfiguration notification to the second AP MLD. The link reconfiguration notification is used to notify the second AP MLD to start the second link. The link reconfiguration notification carries the identifier of the terminal device and at least one of the identifier of the second link and the BSSID.

19. The method according to any one of claims 1 to 18, characterized in that, The first link is the link with the fastest signal attenuation speed among the multiple links supported by the first AP MLD, or the link with the lowest signal quality among the multiple links supported by the first AP MLD, or the link with the largest bandwidth usage among the multiple links supported by the first AP MLD.

20. The method according to any one of claims 1 to 19, characterized in that, The associated message includes at least one of the following: The information includes at least one of the following: association information, authentication information, aggregated session information, physical layer parameters, identity authentication information of the terminal device, link information, encryption key, packet sequence number PN, serial number SN, group temporary key GTK, and communication context information.

21. A roaming method, characterized in that, The roaming method is applied to a communication network, which includes L access point multi-link devices (AP MLDs), where L is any integer greater than or equal to 2. The first AP MLD supports multiple links, including a first link, and the second AP MLD supports multiple links, including a second link. The method includes: The second AP MLD receives an association message from the first AP MLD. The association message corresponds to a terminal device and is used by the first AP MLD to communicate with the terminal device on the first link. The second AP MLD activates the second link, and the associated message is also used for the second AP MLD to communicate with the terminal device on the second link.

22. The method according to claim 21, characterized in that, The first AP MLD supports a third link among multiple links, and the second AP MLD supports a fourth link among multiple links. After the second AP MLD receives the association message from the first AP MLD, the method further includes: The second AP MLD activates the fourth link, and the associated message is also used for the second AP MLD to communicate with the terminal device on the fourth link.

23. The method according to claim 21 or 22, characterized in that, Before the second AP MLD activates the second link, the method further includes: The second AP MLD obtains a second configuration message, which carries a target MAC address, a target BSSID, and a target identifier. The MAC address of the first AP MLD is the target MAC address, the BSSID of the first link is the target BSSID, and the identifier of the first link is the target identifier. According to the second configuration message, the second AP MLD configures the MAC address of the second AP MLD to the target MAC address, configures the BSSID of the second link to the target BSSID, and configures the identifier of the second link to the target identifier.

24. The method according to claim 23, characterized in that, The second AP MLD receives the second configuration message, which includes: The second AP MLD receives the second configuration message from the master control device, which is connected to both the first AP MLD and the second AP MLD. or, The second AP MLD receives the second configuration message from the first AP MLD; or, The second AP MLD locally generates the second configuration message.

25. The method according to claim 24, characterized in that, After the second AP MLD obtains the second configuration message, the method further includes: The second AP MLD sends a first configuration message to the first AP MLD. The first configuration message carries the target MAC address, the target BSSID, the target identifier, and the identifier of the first AP MLD.

26. The method according to any one of claims 21 to 25, characterized in that, The second AP MLD enables the second link by including: The second AP MLD adds the second link; or, The second link of the second AP MLD is used to send downlink messages to the terminal device, and the second AP MLD receives uplink messages from the terminal device via the second link; or, The second link of the second AP MLD has the ability to send downlink messages to any terminal device, and the second AP MLD has the ability to receive uplink messages from any terminal device via the second link.

27. The method according to any one of claims 21 to 26, characterized in that, Before the second AP MLD activates the second link, the method further includes: The second AP MLD sends a shutdown indication message to the first AP MLD. The shutdown indication message is used to indicate that the first AP MLD shuts down the first link. The shutdown indication message carries at least one of the following: the BSSID of the first link, the identifier of the first link, and the identifier of the terminal device.

28. The method according to any one of claims 21 to 27, characterized in that, The second AP MLD enables the second link by including: The second AP MLD receives a link switching request, which is used to instruct the terminal device to roam from the first link to the second link. The link switching request carries at least one of the BSSID of the first link and the identifier of the first link, and also carries the identifier of the terminal device. The second AP MLD activates the second link according to the link switching request.

29. The method according to any one of claims 21 to 27, characterized in that, After the second AP MLD receives the association message from the first AP MLD, the method further includes: The second AP MLD instructs the terminal device to delete the first link; The second AP MLD instructs the terminal device to add the second link.

30. The method according to any one of claims 21 to 27, characterized in that, After the second AP MLD receives the association message from the first AP MLD, the method further includes: The second AP MLD receives the deletion instruction message; The second AP MLD sends a first link reconfiguration notification to the terminal device according to the deletion instruction message. The first link reconfiguration notification carries the identifier of the terminal device and the link deletion instruction, and carries at least one of the identifier of the first link and the BSSID. The link deletion instruction is used to indicate the deletion of the first link. The second AP MLD receives a first link reconfiguration request from the terminal device, the first link reconfiguration request being used to request the deletion of the first link; The second AP MLD sends a link reconfiguration response to the terminal device, the link reconfiguration response being used to indicate the deletion of the first link.

31. The method according to any one of claims 21 to 27, characterized in that, After the second AP MLD activates the second link, the method further includes: The second AP MLD receives a second link reconfiguration request from the terminal device. The second link reconfiguration request is used to request the addition of the second link. The second link reconfiguration request carries the identifier of the terminal device and at least one of the identifier of the second link and the BSSID. The second AP MLD sends a second link reconfiguration response to the terminal device, which is used to indicate the addition of the second link.

32. The method according to claim 31, characterized in that, Before the second AP MLD receives the second link reconfiguration request from the terminal device, the method further includes: The second AP MLD sends a second link reconfiguration notification to the terminal device. The second link reconfiguration notification is used to notify the terminal device to add the second link. The second link reconfiguration notification carries the identifier of the terminal device and at least one of the identifier of the second link and the BSSID.

33. The method according to any one of claims 21 to 27, characterized in that, The second AP MLD enables the second link by including: The second AP MLD receives a link reconfiguration notification, the link reconfiguration notification carrying the identifier of the terminal device, and the link reconfiguration notification carrying at least one of the identifier of the second link and the BSSID; The second AP MLD starts the second link according to the link reconfiguration notification; After the second AP MLD activates the second link, the method further includes: The second AP MLD sends an add instruction to the terminal device according to the link reconfiguration notification, the add instruction being used to indicate the addition of the second link.

34. The method according to any one of claims 21 to 27, characterized in that, After the second AP MLD receives the association message from the first AP MLD, the method further includes: The second AP MLD sends an activation indication frame to the terminal device. The activation indication frame is a beacon frame or a probe response frame. The activation indication frame is used to indicate that the second AP MLD has activated the second link. The second AP MLD receives a first link reconfiguration request from the terminal device, the first link reconfiguration request being used to request the deletion of the first link; The second AP MLD sends a link reconfiguration response to the terminal device, the link reconfiguration response being used to indicate the deletion of the first link.

35. A roaming method, characterized in that, The roaming method is applied to a communication network, which includes a master control device and L access point multi-link devices (AP MLDs), where L is any integer greater than or equal to 2. The master control device is connected to the first AP MLD and the second AP MLD, respectively. The first AP MLD supports multiple links including a first link, and the second AP MLD supports multiple links including a second link. The method includes: The master control device receives an association message from the first AP MLD. The association message corresponds to a terminal device and is used by the first AP MLD to communicate with the terminal device on the first link. The master control device sends the association message to the second AP MLD; The master control device sends a first shutdown indication message to the first AP MLD, the first shutdown indication message being used to instruct the first AP MLD to shut down the first link; The master control device sends a first activation instruction message to the second AP MLD. The first activation instruction message is used to instruct the second AP MLD to activate the second link. The association message is used for the second AP MLD to communicate with the terminal device on the second link.

36. A communication network, characterized in that, The communication network includes L access point multi-link devices (AP MLDs), where L is any integer greater than or equal to 2. The first AP MLD supports multiple links including a first link, and the second AP MLD supports multiple links including a second link. The first AP MLD is used for: Send an association message to the second AP MLD. The association message corresponds to the terminal device. The association message is used for the first AP MLD to communicate with the terminal device on the first link. Close the first link; The second AP MLD is used to activate the second link, and the associated message is also used for the second AP MLD to communicate with the terminal device on the second link.

37. The communication network according to claim 36, characterized in that, The communication network also includes a master control device, which is connected to the first AP MLD and the second AP MLD respectively. The master control device is used to instruct the first AP MLD to shut down the first link and to instruct the second AP MLD to open the second link.

38. An access point multi-link device (AP MLD), characterized in that, The AP MLD includes a processor and a transceiver, wherein the processor is configured to perform any of the processing-related actions of claims 1 to 20, and the transceiver is configured to perform any of the sending-receiving-receiving actions of claims 1 to 20; or, the processor is configured to perform any of the processing-related actions of claims 21 to 34, and the transceiver is configured to perform any of the sending-receiving-receiving-receiving actions of claims 21 to 34.

39. An access point multi-link device (AP MLD), characterized in that, The AP MLD includes a module for performing the method of any one of claims 1 to 20, or the AP MLD includes a module for performing the method of any one of claims 21 to 34.

40. A chip, characterized in that, The chip includes logic circuitry and a communication interface. The communication interface is used to receive data and transmit it to the logic circuitry, or to send data from the logic circuitry to another chip. The logic circuitry is used to perform the processing-related actions of any one of claims 1 to 20, and the communication interface is used to perform the transmission-reception-related actions of any one of claims 21 to 34; or, the logic circuitry is used to perform the processing-related actions of any one of claims 21 to 34, and the communication interface is used to perform the transmission-reception-related actions of any one of claims 21 to 34; or, the logic circuitry is used to perform the processing-related actions of claim 35, and the communication interface is used to perform the transmission-reception-related actions of claim 35.

41. A computer-readable storage medium, characterized in that, Includes computer program instructions, which, when executed by a processor, enable the processor to perform the method as claimed in any one of claims 1 to 20, or the method as claimed in any one of claims 21 to 34, or, as claimed in claim 35.

Images