DATA TRANSMISSION METHODS, DEVICES, AND STORAGE MEDIA

Abstract

The invention relates to a method of data transmission, a device, and a storage medium. The method of data transmission applied to the first network device includes: receiving the first authentication frame sent by the first multi-link device; and forwarding the first authentication frame to the second network device in response to the first authentication frame, which includes an authentication identifier.

Description

Data transmission method, device and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data transmission method, device and storage medium. Background Art

[0002] Under the Ultra High Reliability Access Point Multi-Link Device (UHR AP MLD) architecture, the terminal that establishes a connection with the UHR AP MLD can be a non-AP MLD that supports the Wi-Fi 7 protocol or a non-AP MLD that supports the Wi-Fi 8 protocol. Authentication request frames and other key generation-related frames (such as Extensible Authentication Protocol Over LAN (EAPOL) frames) sent using the Wi-Fi 7 protocol need to be processed in the high Media Access Control (high MAC) layer of the Extremely High Throughput Access Point Multi-Link Device (EHT AP MLD); while non-AP MLDs that support the Wi-Fi 8 protocol and require a multi-link connection method across the EHT AP MLD need to transmit these messages to the high MAC of the UHR AP MLD for processing. There is no signal in the related art to indicate whether the non-AP MLD supports the multi-connection method across EHT AP MLD defined by Wi-Fi 8. Therefore, the EHT AP MLD cannot know whether to forward the received multilink authentication request frame to the high MAC of the UHR AP MLD for processing or process it itself.

[0003] Summary of the Invention

[0004] In view of this, the embodiments of the present application provide a data transmission method, device and storage medium, which solve the technical problem in the related art that it is impossible to determine whether the received first authentication frame is forwarded to the second network device for processing or processed by the first network device itself.

[0005] An embodiment of the present application provides a data transmission method, applied to a first network device, including:

[0006] receiving a first authentication frame sent by a first multi-link device;

[0007] In a case where the first authentication frame includes an authentication identifier, the first authentication frame is forwarded to the second network device.

[0008] An embodiment of the present application provides a data transmission method, applied to a first multi-link device, comprising:

[0009] A first authentication frame is sent to a first network device, so that the first authentication frame is forwarded to a second network device via the first network device if the first authentication frame includes an authentication identifier.

[0010] An embodiment of the present application provides a data transmission method, applied to a second network device, including:

[0011] A first authentication frame forwarded by a first network device is received; wherein the first authentication frame includes an authentication identifier.

[0012] An embodiment of the present application provides a communication device, comprising: a memory, and at least one processor;

[0013] The memory is configured to store at least one program;

[0014] When the at least one program is executed by the at least one processor, the at least one processor implements the method described in any one of the above embodiments.

[0015] The present invention provides a storage medium storing a computer program, which, when executed by a processor, implements the method described in any of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a schematic diagram of a multi-link connection establishment process provided by the related art;

[0017] FIG2 is a schematic diagram illustrating an implementation of an interaction process of a Simultaneous Authentication of Equals (SAE) multi-link authentication method provided by a related art;

[0018] FIG3 is a schematic diagram of an interactive implementation of a four-way handshake process provided by the related art;

[0019] FIG4 is a schematic diagram of a format configuration of an MLO Link K Desktop Environment (KDE) provided by the related art;

[0020] FIG5 is a schematic diagram of a format configuration of MLO GTK KDE provided by the related art;

[0021] FIG6 is a schematic diagram of a format configuration of IGTK KDE provided by the related art;

[0022] FIG7 is a schematic diagram of a format configuration of an MLO BIGTK provided by the related art;

[0023] FIG8 is a configuration diagram of a centralized ultra-high reliability high media access control (UHR upper MAC) UHR AP MLD architecture provided by the related art;

[0024] FIG9 is a schematic diagram of a configuration of a pre-roaming connection model provided by the related art;

[0025] FIG10 is a schematic diagram of a configuration of a connection model in roaming provided by the related art;

[0026] FIG11 is a schematic diagram of a configuration of a connection model after roaming provided by the related art;

[0027] FIG12 is a diagram of a UHR AP MLD network architecture provided by the related art;

[0028] FIG13 is a flowchart of a data transmission method provided in an embodiment of the present application;

[0029] FIG14 is a flowchart of another data transmission method provided in an embodiment of the present application;

[0030] FIG15 is a flowchart of another data transmission method provided in an embodiment of the present application;

[0031] FIG16 is a schematic diagram of an interaction of multi-link authentication of multiple EHT AP MLDs provided in an embodiment of the present application;

[0032] FIG17 is a flowchart of an EHT AP MLD processing a received first authentication frame provided in an embodiment of the present application;

[0033] FIG18 is a schematic diagram of a multi-link four-way handshake interaction of multiple EHT AP MLDs provided in an embodiment of the present application;

[0034] FIG19 is a schematic diagram of a format configuration of an MLO Link KDE provided in an embodiment of the present application;

[0035] FIG20 is a schematic diagram of a format configuration of MLO GTK KDE provided in an embodiment of the present application;

[0036] FIG21 is a schematic diagram of a format configuration of an MLO IGTK KDE provided in an embodiment of the present application;

[0037] FIG22 is a schematic diagram of a format configuration of an MLO BIGTK KDE provided in an embodiment of the present application;

[0038] FIG23 is a structural block diagram of a data transmission device provided in an embodiment of the present application;

[0039] FIG24 is a structural block diagram of another data transmission device provided in an embodiment of the present application;

[0040] FIG25 is a structural block diagram of another data transmission device provided in an embodiment of the present application;

[0041] Figure 26 is a structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The following describes the present application in conjunction with the accompanying drawings. The examples are only used to explain the present application and are not used to limit the scope of the present application.

[0043] The Wi-Fi 7 protocol introduces Multi-Link Operation (MLO) technology. Multi-Link Devices (MLD) include network devices (AP MLDs) and terminal devices (non-AP MLDs). MLDs can transmit data simultaneously on multiple links, improving data throughput and reducing latency.

[0044] After a four-way handshake on a link, the AP MLD and non-AP MLD generate an MLO-level temporary pairwise transient key (PTK) and a link-level group temporary key (GTK), which are used to encrypt and decrypt transmitted unicast data frames and anchor data frames, respectively, ensuring the security of data transmission. For example, Figure 1 is a schematic diagram of a multi-link connection establishment process provided by related art. As shown in Figure 1, both the AP MLD and non-AP MLD include three links operating at 2.4 GHz, 5 GHz, and 6 GHz. The AP MLD and non-AP MLD complete the authentication, connection, and four-way handshake processes on the 2.4 GHz link. After establishing the multi-link connection, data can be transmitted on the three links (Link 1, Link 2, and Link 3).

[0045] During the multi-link authentication process, the SAE protocol can be used to exchange relevant information. SAE protocol messages include commit messages and confirm messages. Figure 2 is a schematic diagram of the implementation process of the SAE multi-link authentication method provided by related technologies. As shown in Figure 2, the implementation process is described as follows:

[0046] Step 1: The Non-AP MLD sends an Authentication frame to the AP MLD, which includes the supplicant MAC address and an SAE commit message (commit message for short).

[0047] The commit message includes the scalar S (Ssta) and element E (Esta) generated by the non-AP MLD end.

[0048] Step 2: The AP MLD sends an Authentication frame to the non-AP MLD, which includes the Authenticator MAC address and an SAE commit message.

[0049] The commit message contains the scalar S (Sap) and element E (Eap) generated by the AP MLD side.

[0050] In step 3, the non-AP MLD and AP MLD use the locally stored shared key information, the supplicant MAC address, and the authenticator MAC address to generate the key element P according to a specific algorithm.

[0051] Step 4: On the non-AP MLD side, K1 is generated using the key elements P, S(ap), E(ap) and the local random number r(sta) according to a certain key algorithm.

[0052] Step 5: At the AP MLD end, K2 is generated using the key elements P, S(sta), E(sta) and the local random number r(ap) according to a certain key algorithm.

[0053] In step 6, the non-AP MLD uses K1 to generate K3, and uses K3, S(ap), E(ap), S(sta), and E(sta) according to a certain secret key algorithm to generate a confirm message (Csta), which is sent to the AP MLD using an Authentication frame.

[0054] In step 7, the AP MLD uses K2 to generate K4. It then uses K4, S(ap), E(ap), S(sta), and E(sta) according to a specific key algorithm to generate a confirm message (Cap). If (Cap) matches (Csta), and if they match, the AP MLD sends the Cap to the non-AP MLD using an authentication frame.

[0055] Step 8: On the non-AP MLD side, Csta is matched with the received Cap. If they are the same, a local key K1=K2 is generated, and K1 / K2 is used as the pairwise master key (PMK).

[0056] Figure 3 is a schematic diagram of the interaction implementation of a four-way handshake process provided by related technologies. After completing the exchange of association request frames and response frames, the AP MLD sends a data frame containing an Extensible Authentication Protocol over LANs (EAPOL)-KEY message to the non-AP MLD on one of the associated links, initiating the four-way handshake. As shown in Figure 3, the implementation process of the four-way handshake is as follows:

[0057] Step 1: The AP MLD sends the first EAPOL-KEY frame (EAPOL-1 for short) to the non-AP MLD. The frame contains the authenticator's MAC address and a random number (A-nonce) generated by the authenticator.

[0058] In step 2, the non-AP MLD sends the second EAPOL-KEY frame (EAPOL-2) to the AP MLD. This frame contains the supplicant's MAC address, a random number (S-nonce) generated by the supplicant, and the Robust Security Network Element (RSN) (RSNXE) information requested by the non-AP MLD for each link. Figure 4 illustrates the format configuration of an MLO Link KDE, as provided in related art. As shown in Figure 4, the MLO Link KDE field includes at least the Robust Security Network Element (RSNE) and the Extended Robust Security Network Element (RSNXE).

[0059] In step 3, the AP MLD sends the third EAPOL-KEY frame (EAPOL-3 for short) to the non-AP MLD. This frame contains GTK information, IGTK information, BIGTK information, the RSN of the requested link on the AP MLD side, RSNXE information, and integrity check information. Figure 5 is a schematic diagram of the format configuration of an MLO GTK KDE provided by the related art. As shown in Figure 5, the GTK KDE field includes at least the Link ID field. Figure 6 is a schematic diagram of the format configuration of an IGTK KDE provided by the related art. As shown in Figure 6, the IGTK KDE field includes at least the Link ID field and the IGTK field. Figure 7 is a schematic diagram of the format configuration of an MLO BIGTK provided by the related art. As shown in Figure 7, the BIGTK KDE field includes at least the Link ID field and the BIGTK field.

[0060] In step 4, the non-AP MLD sends the fourth EAPOL-KEY frame (EAPOL-4 for short) to the AP MLD, which contains information for integrity verification.

[0061] The Wi-Fi 8 protocol proposes that UHR AP MLDs can be deployed in different locations for the subordinate APs of the same UHR AP MLD, solving the latency issue that occurs when devices roam. Furthermore, channel utilization issues can be addressed by collaborating with multiple subordinate APs within the same UHR AP MLD.

[0062] A centralized UHR AP MLD architecture is provided in the seamless roaming solution under the non-parallel AP MLD architecture. FIG8 is a configuration diagram of a centralized UHR upper MAC UHR AP MLD architecture provided by the related art. As shown in FIG8, a UHR AP MLD includes multiple EHT AP MLDs (e.g., EHT AP MLD1, EHT AP MLD2, ..., EHT AP MLD X) deployed on different physical device nodes and a UHR upper MAC. The UHR non-AP MLD can establish a link connection with the Low Media Access Control (Low MAC) of any node without switching the connected network, thus solving the data transmission delay problem caused by network switching.

[0063] Based on the framework of Figure 8, a complete model of the roaming process is provided, including three stages: pre-roaming, roaming, and post-roaming. Figure 9 is a configuration diagram of a pre-roaming connection model provided by the related art; Figure 10 is a configuration diagram of a roaming connection model provided by the related art; and Figure 11 is a configuration diagram of a post-roaming connection model provided by the related art. As shown in Figure 9, before roaming, a non-AP MLD selects a target access point group (AP Group) and a target link (link4, link5); as shown in Figure 10, during roaming, the non-AP MLD disconnects a link (AP1) with AP Group 1 and establishes a connection with AP Group 2 (AP4). The process is then repeated, disconnecting a link (AP2) with AP Group 1 and establishing a connection with AP Group 2 (AP5), ultimately completing the roaming process, as shown in Figure 11.

[0064] Figure 12 is a UHR AP MLD network architecture diagram provided by related technologies. As shown in Figure 12, under the UHR AP MLD architecture, the multi-link authentication and key generation process across EHT AP MLDs has the following problems:

[0065] First, the terminal connected to the UHR AP MLD can be a non-AP MLD that supports the Wi-Fi 7 protocol or the Wi-Fi 8 protocol. The authentication request frame and other key generation-related frames (such as EAPOL frames) sent by Wi-Fi 7 need to be processed by the high MAC of the EHT AP MLD; and the non-AP MLD that supports the multi-link connection mode of Wi-Fi 8 across EHT AP MLD needs to transmit these messages to the UHR AP MLD high MAC for processing. However, there is currently no signal to indicate whether the non-AP MLD supports the multi-link connection mode across EHT AP MLD defined by Wi-Fi 8. Therefore, the EHT AP MLD cannot know whether the received multi-link authentication request frame is forwarded to the UHR AP MLD high MAC for processing or processed by itself.

[0066] Second, EHT AP MLD1 and EHT AP MLD2 each have their own MLD MAC addresses, but these two MLD MAC addresses cannot uniquely identify a UHR AP MLD and therefore cannot be sent as the authentication address in the authentication response frame to the non-AP MLD.

[0067] Third, during the four-way handshake of the initial connection, the UHR AP MLD needs to send the GTK, IGTK, and BIGTK of each link establishing multiple connections to the non-AP MLD. However, since each EHT AP MLD uniquely numbers its attached links (Link IDs), it is possible that multiple EHT AP MLDs may have the same Link ID when connecting multiple links. The non-AP MLD cannot use the existing Link IDs to distinguish the KEY information of different links, and thus cannot decrypt and perform integrity verification on multicast packets transmitted on the corresponding links.

[0068] Fourth, during roaming, the UHR AP MLD needs to send the GTK, IGTK, and BIGTK of the newly established multi-connected links to the non-AP MLD to promptly release the resources corresponding to the dismantled links. However, since each EHT AP MLD uniquely numbers its attached links, and the link numbers range from 0 to 14 or 0 to 15, there is a scenario where two EHT AP MLDs have the same Link ID. The UHR AP MLD cannot use the 802.11be protocol Link ID to determine which EHT AP MLD has the multicast-related key for the link.

[0069] For ease of understanding, the first network device provided in the embodiment of the present application may be an EHT AP MLD; the second network device may be a UHR AP MLD; and the first multi-link device may be a non-AP MLD (eg, UHR non-AP MLD or EHT non-AP MLD).

[0070] In one embodiment, Figure 13 is a flowchart of a data transmission method provided by an embodiment of the present application. This embodiment is applied to automatically determine whether a first authentication frame needs to be processed by a first network device. This embodiment can be executed by the first network device. As shown in Figure 13, this embodiment includes: S110-S120.

[0071] S110: Receive a first authentication frame sent by a first multi-link device.

[0072] S120: When the first authentication frame includes an authentication identifier, forward the first authentication frame to the second network device.

[0073] In an embodiment, the authentication identifier is used to indicate whether the first authentication frame is forwarded to the second network device. It can also be used to indicate whether the first authentication frame is processed by the first network device or the second network device. After the first multi-link device sends the first authentication frame containing the authentication identifier to the first network device, the first network device directly forwards the first authentication frame to the second network device, and the second network device parses and processes the first authentication frame. In one embodiment, if the first authentication frame does not contain the authentication identifier, the first authentication frame is directly processed. If the first authentication frame sent by the first multi-link device does not contain the authentication identifier, the first network device directly parses and processes the first authentication frame.

[0074] In one embodiment, the data transmission method applied to the first network device further includes: receiving a second authentication frame including an authentication identifier sent by the second network device; and forwarding the second authentication frame to the first multi-link device. After the first multi-link device sends the first authentication frame including the authentication identifier to the first network device, the first network device directly forwards the first authentication frame including the authentication identifier to the second network device, and the second network device parses and processes the first authentication frame to generate a corresponding second authentication frame including the authentication identifier, and sends the second authentication frame including the authentication identifier to the first network device via a backhaul link. The second authentication frame including the authentication identifier is then directly forwarded to the first multi-link device via the first network device.

[0075] In one embodiment, the data transmission method applied to the first network device further includes: parsing the first authentication frame to obtain a corresponding first authentication submission message or first authentication confirmation message; and, if the first authentication frame includes an authentication identifier, forwarding the first authentication submission message or first authentication confirmation message to the second network device. After the first multi-link device sends the first authentication frame to the first network device, the first network device may parse the first authentication frame including the authentication identifier to obtain a corresponding first authentication submission message or first authentication confirmation message, and, if the first authentication frame includes the authentication identifier, forwarding the first authentication submission message or first authentication confirmation message to the second network device.

[0076] In one embodiment, the data transmission method applied to the first network device also includes: receiving a second authentication submission message or a second authentication confirmation message sent by the second network device; combining the received authentication identifier or the self-generated authentication identifier with the second authentication submission message or the second authentication confirmation message to form a corresponding second authentication frame; and forwarding the second authentication frame to the first multi-link device. After the first multi-link device sends the first authentication frame to the first network device, the first network device can parse the first authentication frame containing the authentication identifier to obtain the corresponding first authentication submission message or first authentication confirmation message, and when the first authentication frame contains the authentication identifier, the first network device forwards the first authentication submission message or the first authentication confirmation message to the second network device, and the second network device processes the first authentication submission message or the first authentication confirmation message to obtain the corresponding second authentication submission message or second authentication confirmation message; then the second network device sends the second authentication submission message or the second authentication confirmation message to the first network device, so that the first network device combines the authentication identifier sent by the second network device with the second authentication submission message or the second authentication confirmation message to generate a corresponding second authentication frame containing the authentication identifier, or so that the first network device combines the authentication identifier generated by itself with the second authentication submission message or the second authentication confirmation message to generate a corresponding second authentication frame containing the authentication identifier; then the second authentication frame containing the authentication identifier is directly forwarded to the first multi-link device through the first network device.

[0077] In one example, when a first authentication submission message is parsed from a first authentication frame, the second network device generates a corresponding second authentication submission message based on the first authentication submission message; when a first authentication confirmation message is parsed from the first authentication frame, the second network device generates a corresponding second authentication confirmation message based on the first authentication confirmation message.

[0078] In one embodiment, the authentication identifier includes one of the following: a Media Access Control (MAC) address of the first network device; a MAC address of the second network device; or roaming capability indication information. The roaming capability indication information is used to indicate whether UHR roaming capability is available. In one example, if the roaming capability indication information is 1, the first authentication frame is directly forwarded to the second network device via the first network device, and the second network device processes the first authentication frame. If the roaming capability indication information is 0, the first authentication frame may be processed by the first network device.

[0079] In one embodiment, the data transmission method applied to the first network device further includes: receiving a first LAN extended authentication frame sent by the second network device; wherein the first LAN extended authentication frame carries at least the MAC address of the second network device; and forwarding the first LAN extended authentication frame to the first multi-link device. Each second network device is configured with a uniquely identified MAC address. In the first LAN extended authentication frame, the MAC address of the second network device can be used to fill the authentication address field in the first LAN extended authentication frame. The second network device generates the first LAN extended authentication frame and sends the first LAN extended authentication frame to the first network device via a backhaul link. The first network device can send the first LAN extended authentication frame to the first multi-link device via a 2.4GHz or 5GHz associated link.

[0080] In one embodiment, the data transmission method applied to the first network device further includes: receiving a second LAN extended authentication frame sent by the first multi-link device; wherein the second LAN extended authentication frame carries at least link identifier information consisting of the first network device identifier and the link identifier; and forwarding the second LAN extended authentication frame to the second network device. After the first multi-link device receives the first LAN extended authentication frame sent by the first network device, the second LAN extended authentication frame is sent to the first network device via a 2.4GHz or 5GHz associated link, so that the first network device forwards the second LAN extended authentication frame to the second network device via a backhaul link. In one example, the second LAN extended authentication frame contains at least link identifier information consisting of the first network device identifier and the link identifier, so that information transmitted on different links on different first network devices can be accurately distinguished.

[0081] In one embodiment, the first network device identifier includes at least one of the following: a MAC address of the first network device; or a first network device index. The first network device identifier is an identifier used to uniquely identify each first network device. In one example, the first network device identifier can be the MAC address of the first network device or the device index of the first network device.

[0082] In one embodiment, a data transmission method applied to a first network device further includes: receiving a third LAN extended authentication frame sent by a second network device; wherein the third LAN extended authentication frame includes at least the first network device identifier, a link identifier, and a group temporary key (GTK) for the link; and forwarding the third LAN extended authentication frame to the first multi-link device. The second network device generates the third LAN extended authentication frame and sends the third LAN extended authentication frame to the first network device via a backhaul link, wherein the third LAN extended authentication frame includes at least the first network device identifier, the link identifier, and the group temporary key for the link, so that the second network device can accurately determine on which first network device the link key is to be verified through the link identifier.

[0083] In one embodiment, the third LAN extended authentication frame further includes a GTK field; the frame structure of the GTK field includes at least a first device identifier field, which is used to indicate the first network device identifier corresponding to the third LAN extended authentication frame. During the four-way handshake process of the initial connection, the second network device may send the third LAN extended authentication frame carrying at least the first device identifier to the first network device, and the first network device may forward the third LAN extended authentication frame carrying at least the first device identifier to the first multi-link device. The first multi-link device can then distinguish authentication information on different links using the first device identifier, and can then decrypt and perform integrity verification on messages transmitted on the corresponding links.

[0084] In one embodiment, the third LAN extended authentication frame further includes: an integrity group temporary key (Integrity Group Temporal Key, IGTK) information field, a beacon frame integrity group temporary key (Beacon Integrity Group Temporal Key, BIGTK) information field, an RSNE information field, and an RSNXE information field;

[0085] Among them, the frame structure of the IGTK information field, the BIGTK information field, the RSNE field, and the RSNXE information field includes at least a first device identifier field, which is used to indicate the first network device identifier corresponding to the third LAN extended authentication frame. During the four-way handshake process of the initial connection, the second network device can send the GTK, IGTK, and BIGTK on each link for establishing multiple connections, as well as the third LAN extended authentication frame with the first device identifier, to the first network device, and forward the third LAN extended authentication frame carrying at least the first device identifier to the first multi-link device through the first network device, so that the first multi-link device can distinguish the authentication information on different links through the first device identifier, and then decrypt and verify the integrity of the messages transmitted on the corresponding links.

[0086] In one embodiment, FIG14 is a flowchart of another data transmission method provided by an embodiment of the present application. This embodiment can be performed by a first multi-link device. As shown in FIG14 , this embodiment includes: S210.

[0087] S210: Send a first authentication frame to the first network device, so that when the first authentication frame includes an authentication identifier, the first authentication frame is forwarded to the second network device through the first network device.

[0088] In one embodiment, the authentication identifier includes one of the following: a MAC address of the first network device; a MAC address of the second network device; or roaming capability indication information.

[0089] In one embodiment, the data transmission method applied to the first multi-link device further includes:

[0090] A first LAN extended authentication frame forwarded by a first network device is received; wherein the first LAN extended authentication frame carries at least a MAC address of a second network device.

[0091] In one embodiment, the data transmission method applied to the first multi-link device further includes:

[0092] A second LAN extended authentication frame is sent to the first network device; wherein the second LAN extended authentication frame carries at least link identifier information consisting of the first network device identifier and the link identifier.

[0093] In one embodiment, the data transmission method applied to the first multi-link device further includes:

[0094] A third local area network extended authentication frame forwarded by the first network device is received; wherein the third local area network extended authentication frame at least includes the first network device identifier, the link identifier, and the group temporary key on the link.

[0095] In one embodiment, the first network device identifier includes at least one of the following: a MAC address of the first network device; or a first network device index.

[0096] In one embodiment, the third LAN extended authentication frame further includes: a GTK field; the frame structure of the GTK field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0097] In one embodiment, the third LAN extended authentication frame further includes: an IGTK information field, a BIGTK information field, an RSNE information field, and an RSNXE information field;

[0098] The frame structure of the IGTK information field, the BIGTK information field, the RSNE field, and the RSNXE information field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0099] In one embodiment, when an operation other than a four-way handshake occurs, the data transmission method applied to the first multi-link device further includes:

[0100] Receive first key information on a new link sent by a second network device; the first key information includes at least link identifier information. The first key information refers to GTK, IGTK, or BIGTK information. When the first multi-link device roams, such as when a link is dynamically added or switched, the second network device sends the first key information on the new link to the first multi-link device, and the first key information includes at least link identifier information and the corresponding first key information on the link. The link identifier information may be a link identifier across multi-link devices.

[0101] It should be noted that the explanation of parameters such as the first authentication frame, authentication identifier, first LAN extended authentication frame, second LAN extended authentication frame, and third LAN extended authentication frame involved in the first multi-link device can be found in the description of the corresponding parameters applied to the first network device above, and will not be repeated here.

[0102] In one embodiment, FIG15 is a flowchart of another data transmission method provided by an embodiment of the present application. This embodiment can be executed by a second network device. As shown in FIG15 , this embodiment includes: S310.

[0103] S310: Receive a first authentication frame forwarded by a first network device; wherein the first authentication frame includes an authentication identifier.

[0104] In one embodiment, the authentication identifier includes one of the following: a MAC address of the first network device; a MAC address of the second network device; or roaming capability indication information.

[0105] In one embodiment, the data transmission method applied to the second network device further includes:

[0106] A first LAN extended authentication frame is sent to the first network device; wherein the first LAN extended authentication frame carries at least a MAC address of the second network device.

[0107] In one embodiment, the data transmission method applied to the second network device further includes:

[0108] A second LAN extended authentication frame forwarded by the first network device is received; wherein the second LAN extended authentication frame carries at least link identifier information consisting of the first network device identifier and the link identifier.

[0109] In one embodiment, the data transmission method applied to the second network device further includes:

[0110] A third local area network extended authentication frame is sent to the first network device; wherein the third local area network extended authentication frame includes at least the first network device identifier, the link identifier, and the group temporary key on the link.

[0111] In one embodiment, the first network device identifier includes at least one of the following: a MAC address of the first network device; or a first network device index.

[0112] In one embodiment, the third LAN extended authentication frame further includes: a GTK field; the frame structure of the GTK field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0113] In one embodiment, the third LAN extended authentication frame further includes: an IGTK information field, a BIGTK information field, an RSNE information field, and an RSNXE information field;

[0114] The frame structure of the IGTK information field, the BIGTK information field, the RSNE field, and the RSNXE information field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0115] In one embodiment, when an operation other than a four-way handshake occurs, the data transmission method applied to the second network device further includes:

[0116] Sending first key information on the new link to the first multi-link device; wherein the first key information at least includes link identifier information.

[0117] It should be noted that, for the explanation of parameters such as the first authentication frame, authentication identifier, first LAN extended authentication frame, second LAN extended authentication frame, and third LAN extended authentication frame involved in the second network device, please refer to the description of the corresponding parameters applied to the first network device or the first multi-link device above, and will not be repeated here.

[0118] In the following embodiments, the authentication process and the four-way handshake process are described by taking the first network device as an EHT AP MLD, the second network device as a UHR AP MLD, and the first multi-link device as a non-AP MLD as an example.

[0119] Each UHR AP MLD consists of a UHR upper MAC (including the authenticator running on it) and multiple EHT AP MLDs at different physical locations. The EHT AP MLD establishes a backhaul link with the UHR upper MAC via a wired or wireless method.

[0120] On this basis, the embodiments of the present application propose a multi-link authentication and four-way handshake scheme for multiple EHT AP MLDs under the UHR AP MLD architecture. This scheme can not only establish multi-link connections between a non-AP MLD and an EHT AP MLD under the UHR AP MLD, but also establish multi-link connections between a non-AP MLD and multiple EHT AP MLDs under the UHR AP MLD.

[0121] In one embodiment, FIG16 is an interactive diagram of multi-link authentication of multiple EHT AP MLDs provided in an embodiment of the present application. In this embodiment, the multi-link authentication process of multiple EHT AP MLDs is described by taking the first multi-link device as a non-AP MLD, the first network device as an EHT AP MLD1, the second network device as a UHR AP MLD, the EHT AP MLD1 including two APs (AP1 and AP2), and the non-AP MLD including two STAs (STA1 and STA2) as an example. As shown in FIG16, the multi-link connection authentication process of multiple EHT AP MLDs is as follows:

[0122] In step 1, the non-AP MLD sends a first authentication frame (referred to as authentication for short) including an authentication identifier and a first authentication submission message to the EHT AP MLD1 via a first link (Link1).

[0123] Step 2: After receiving the first authentication frame through Link 1, EHT AP MLD 1 parses the first authentication frame to obtain the authentication identifier, and then sends the frame to UHR AP MLD through the backhaul link.

[0124] Step 3: The UHR AP MLD parses and processes authentication1, generates a second authentication frame (referred to as authentication for short) including a second authentication submission message, and sends the frame to the EHT AP MLD1 via the backhaul link.

[0125] Step 4: EHT AP MLD1 forwards the second authentication frame to the non-AP MLD.

[0126] (5) Repeat the above steps to complete the interaction between the first authentication frame containing the first authentication confirmation message generated by the non-AP MLD side and the second authentication frame containing the second authentication confirmation message generated by the UHR AP MLD side.

[0127] The steps shown in FIG. 16 are further described as follows:

[0128] In some application instances, the authentication identifier is a MAC address of a UHR AP MLD or a UHR non-AP MLD; in other application instances, the authentication identifier is UHR seamless roaming capability indication information.

[0129] In some application examples, EHT AP MLD1 receives an authentication frame including an authentication identifier on the first link, parses the authentication frame, and forwards the information carried therein (such as commit information or confirm information) to the UHR AP MLD. Similarly, EHT AP MLD1 receives authentication information (such as commit information or confirm information) from the UHR AP MLD on the backhaul link, assembles the corresponding authentication frame on the EHT AP MLD1, and sends it to the non-AP MLD via the first link.

[0130] In some application examples, EHT AP MLD1 receives an authentication frame containing an authentication identifier on the first link, does not parse the authentication frame, and forwards the entire authentication frame to the UHR AP MLD. Similarly, EHT AP MLD1 receives an authentication frame from the UHR AP MLD on the backhaul link, does not parse the frame, and sends it to the non-AP MLD via the first link. This process may involve changes to the protocol frame header.

[0131] In some application examples, when the EHT AP MLD receives an authentication frame that does not include an authentication identifier on the first link, the frame will be processed on the authentication of the EHT AP MLD, and will not be forwarded to the UHR AP MLD.

[0132] In one example, FIG17 is a flowchart of an EHT AP MLD processing a received first authentication frame provided by an embodiment of the present application. As shown in FIG17 , the EHT AP MLD processing process for the received first authentication frame includes:

[0133] S410: The EHT AP MLD receives a first authentication frame.

[0134] S420: Check whether the first authentication frame contains an authentication identifier. If so, execute S430; if not, execute S440.

[0135] S430: Forward the first authentication frame to the UHR AP MLD.

[0136] S440: Send the first authentication frame to the authenticator of the EHT AP MLD for processing.

[0137] In one example, Figure 18 is a schematic diagram of the interaction of a multi-link four-way handshake for multiple EHT AP MLDs provided in an embodiment of the present application. In this embodiment, the interaction process of the multi-link four-way handshake for multiple EHT AP MLDs is described by taking communication on a 2.4 GHz link as an example, where the first LAN extended authentication frame is an EAPOL-1 frame, the second LAN extended authentication frame is an EAPOL-2 frame, the third LAN extended authentication frame is an EAPOL-3 frame, and the fourth LAN extended authentication frame is an EAPOL-4 frame. As shown in Figure 18, the implementation process of the multi-link four-way handshake for multiple EHT AP MLDs is described as follows:

[0138] Step 1: The first network device (UHR AP MLD) generates an EAPOL-1 frame and sends it to the second network device (EHT AP MLD1) via a backhaul link. The EAPOL-1 frame contains at least an authenticator MAC and an A-nonce.

[0139] Step 2: EHT AP MLD1 sends an EAPOL-1 frame to the first multi-link device (non-AP MLD) via the 2.4 GHz associated link.

[0140] Step 3: After receiving the EAPOL-1 frame, the Non-AP MLD sends an EAPOL-2 frame to the EHT AP MLD1 through the 2.4 GHz link.

[0141] The EAPOL-2 frame contains at least the supplicant MAC address, S-Nonce, the unique identifier of the requested link, and the RSNE and RSNXE of the corresponding non-AP MLD side link.

[0142] Step 4: EHT AP MLD1 sends the EAPOL-2 frame to UHR AP MLD via the backhaul link.

[0143] In step 5, the UHR AP MLD generates an EAPOL-3 frame and sends it to the EHT AP MLD1 via the backhaul link. The EAPOL-3 frame contains at least multiple connection link identifiers and their GTK information, as well as RSNE and RSNXE information corresponding to the UHR AP MLD-side link, and Message Integrity Check (MIC) information.

[0144] In step 6, EHT AP MLD1 may send EAPOL-3 frames to the non-AP MLD via the 2.4 GHz associated link.

[0145] In step 7, the Non-AP MLD may send an EAPOL-4 frame to the EHT AP MLD1 through the 2.4 GHz associated link. The EAPOL-4 frame includes at least the MIC information.

[0146] Step 8: EHT AP MLD1 sends the EAPOL-4 frame to UHR AP MLD via the backhaul link.

[0147] The steps shown in FIG18 are further described as follows:

[0148] In some application examples, the UHR AP MLD is configured with a unique MAC address, and the authenticator address field in the EAPOL-1 frame is populated with the UHR AP MLD MAC address.

[0149] In some application instances, the link identifier information is identified using an EHT AP MLD identifier (i.e., the first network device identifier in the above embodiment) and a Link ID (i.e., the link identifier in the above embodiment), and the EHT AP MLD identifier is an EHT AP MLD MAC address or an EHT AP MLD index (abbreviated as MLD index).

[0150] In some application examples, RSNE and RSNXE information in EAPOL-2 frames. Figure 19 is a configuration diagram of an MLO Link KDE format provided by an embodiment of the present application. As shown in Figure 19, the MLO Link KDE includes at least a first network device identifier (ie, MLD index).

[0151] In some application examples, the GTK information format in EAPOL-3 is shown in Figure 20, and the RSNE and RSNXE information formats are shown in Figure 19. Figure 20 is a schematic diagram of the format configuration of an MLO GTK KDE provided in an embodiment of the present application. As shown in Figure 20, the MLO GTK KDE format includes at least a first network device identifier (i.e., an MLD index).

[0152] In some application examples, EAPOL-3 may also include IGTK and BIGTK information, the information formats of which are shown in Figures 21 and 22, respectively. Figure 21 is a schematic diagram of the format configuration of an MLO IGTK KDE provided in an embodiment of the present application. As shown in Figure 21, the IGTK KDE format includes at least a first network device identifier (i.e., an MLD index). Figure 22 is a schematic diagram of the format configuration of an MLO BIGTK KDE provided in an embodiment of the present application. As shown in Figure 22, the MLO BIGTK format includes at least a first network device identifier (i.e., an MLD index).

[0153] In some application examples, in roaming scenarios, such as when dynamically adding a link or switching a link, when the UHR AP MLD sends the GTK, IGTK, and BIGTK information on the new link to the non-AP MLD, it includes the cross-MLD link identifier and the GTK, IGTK, and BIGTK information corresponding to the link.

[0154] In one embodiment, FIG23 is a block diagram of a data transmission device provided in an embodiment of the present application. This embodiment is applied to a first network device. As shown in FIG23 , the data transmission device in this embodiment includes: a receiver 510 and a forwarder 520.

[0155] The receiver 510 is configured to receive a first authentication frame sent by a first multi-link device.

[0156] The forwarder 520 is configured to forward the first authentication frame to the second network device if the first authentication frame includes the authentication identifier.

[0157] In one embodiment, when the first authentication frame does not include the authentication identifier, the first authentication frame is directly processed.

[0158] In one embodiment, the data transmission apparatus applied to the first network device further includes:

[0159] The receiver 510 is further configured to receive a second authentication frame including an authentication identifier sent by a second network device;

[0160] The forwarder 520 is further configured to forward the second authentication frame to the first multi-link device.

[0161] In one embodiment, the data transmission apparatus applied to the first network device further includes:

[0162] a parsing module configured to parse the first authentication frame to obtain a corresponding first authentication submission message or a first authentication confirmation message;

[0163] The forwarder 520 is further configured to forward the first authentication submission message or the first authentication confirmation message to the second network device when the first authentication frame includes the authentication identifier.

[0164] In one embodiment, the data transmission apparatus applied to the first network device further includes:

[0165] The receiver 510 is further configured to receive a second authentication submission message or a second authentication confirmation message sent by the second network device;

[0166] a composition module configured to combine a received authentication identifier or a self-generated authentication identifier with a second authentication submission message or a second authentication confirmation message to form a corresponding second authentication frame;

[0167] The forwarder 520 is further configured to forward the second authentication frame to the first multi-link device.

[0168] In one embodiment, the authentication identifier includes one of the following: a media access control (MAC) address of the first network device; a MAC address of the second network device; or roaming capability indication information.

[0169] In one embodiment, the data transmission apparatus applied to the first network device further includes:

[0170] The receiver 510 is further configured to receive a first LAN extended authentication frame sent by the second network device; wherein the first LAN extended authentication frame carries at least a MAC address of the second network device;

[0171] The forwarder 520 is further configured to forward the first LAN extended authentication frame to the first multi-link device.

[0172] In one embodiment, the data transmission apparatus applied to the first network device further includes:

[0173] The receiver 510 is further configured to receive a second LAN extended authentication frame sent by the first multi-link device; wherein the second LAN extended authentication frame carries at least link identifier information consisting of the first network device identifier and the link identifier;

[0174] The forwarder 520 is further configured to forward the second LAN extended authentication frame to the second network device.

[0175] In one embodiment, the first network device identifier includes at least one of the following: a MAC address of the first network device; or a first network device index.

[0176] In one embodiment, the data transmission apparatus applied to the first network device further includes:

[0177] The receiver 510 is further configured to receive a third LAN extended authentication frame sent by the second network device; wherein the third LAN extended authentication frame includes at least the first network device identifier, the link identifier, and the group temporary key on the link;

[0178] The forwarder 520 is further configured to forward the third LAN extended authentication frame to the first multi-link device.

[0179] In one embodiment, the frame structure of the group temporary key includes at least a first device identifier field, which is used to indicate the first network device identifier corresponding to the third LAN extended authentication frame.

[0180] In one embodiment, the third LAN extended authentication frame further includes: an integrity group temporary key IGTK information field, a beacon frame integrity group temporary key BIGTK information field, a robust security network element RSNE information field, and an extended robust security network element RSNXE information field;

[0181] The frame structure of the IGTK information field, the BIGTK information field, the RSNE field, and the RSNXE information field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0182] The data transmission device provided in this embodiment is configured to implement the data transmission method applied to the first network device in the embodiment shown in FIG13 . The implementation principle and technical effects of the data transmission device provided in this embodiment are similar and will not be described in detail here.

[0183] In one embodiment, FIG24 is a block diagram of another data transmission device provided by an embodiment of the present application. This embodiment is applied to a first multi-link device. As shown in FIG24 , the data transmission device in this embodiment includes: a transmitter 610.

[0184] The transmitter 610 is configured to send a first authentication frame to the first network device, so that when the first authentication frame includes an authentication identifier, the first authentication frame is forwarded to the second network device via the first network device.

[0185] In one embodiment, the authentication identifier includes one of the following: a MAC address of the first network device; a MAC address of the second network device; or roaming capability indication information.

[0186] In one embodiment, the data transmission apparatus applied to the first multi-link device further includes:

[0187] The receiver is configured to receive a first LAN extended authentication frame forwarded by the first network device; wherein the first LAN extended authentication frame at least carries a MAC address of the second network device.

[0188] In one embodiment, the data transmission apparatus applied to the first multi-link device further includes:

[0189] The transmitter 610 is further configured to send a second LAN extended authentication frame to the first network device; wherein the second LAN extended authentication frame carries at least link identifier information consisting of the first network device identifier and the link identifier.

[0190] In one embodiment, the data transmission apparatus applied to the first multi-link device further includes:

[0191] The receiver is further configured to receive a third LAN extended authentication frame forwarded by the first network device; wherein the third LAN extended authentication frame at least includes the first network device identifier, the link identifier, and the group temporary key on the link.

[0192] In one embodiment, the first network device identifier includes at least one of the following: a MAC address of the first network device; or a first network device index.

[0193] In one embodiment, the third LAN extended authentication frame further includes: a GTK field; the frame structure of the GTK field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0194] In one embodiment, the third LAN extended authentication frame further includes: an IGTK information field, a BIGTK information field, an RSNE information field, and an RSNXE information field;

[0195] The frame structure of the IGTK information field, the BIGTK information field, the RSNE field, and the RSNXE information field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0196] In one embodiment, when an operation other than a four-way handshake occurs, the data transmission apparatus applied to the first multi-link device further includes:

[0197] The receiver is further configured to receive first key information on the new link sent by the second network device; wherein the first key information at least includes link identifier information.

[0198] The data transmission device provided in this embodiment is configured to implement the data transmission method applied to the first multi-link device in the embodiment shown in FIG. 14 . The implementation principle and technical effects of the data transmission device provided in this embodiment are similar and will not be described in detail here.

[0199] In one embodiment, FIG25 is a block diagram of another data transmission device provided in an embodiment of the present application. This embodiment is applied to a second network device. As shown in FIG25 , the data transmission device in this embodiment includes: a receiver 710.

[0200] The receiver 710 is configured to receive a first authentication frame forwarded by a first network device; wherein the first authentication frame includes an authentication identifier.

[0201] In one embodiment, the authentication identifier includes one of the following: a MAC address of the first network device; a MAC address of the second network device; or roaming capability indication information.

[0202] In one embodiment, the data transmission apparatus applied to the second network device further includes:

[0203] The transmitter is configured to send a first LAN extended authentication frame to the first network device; wherein the first LAN extended authentication frame carries at least a MAC address of the second network device.

[0204] In one embodiment, the data transmission apparatus applied to the second network device further includes:

[0205] The receiver 710 is further configured to receive a second LAN extended authentication frame forwarded by the first network device; wherein the second LAN extended authentication frame at least carries link identifier information consisting of the first network device identifier and the link identifier.

[0206] In one embodiment, the data transmission apparatus applied to the second network device further includes:

[0207] The transmitter is further configured to send a third LAN extended authentication frame to the first network device; wherein the third LAN extended authentication frame at least includes the first network device identifier, the link identifier, and the group temporary key on the link.

[0208] In one embodiment, the first network device identifier includes at least one of the following: a MAC address of the first network device; or a first network device index.

[0209] In one embodiment, the third LAN extended authentication frame further includes: a GTK field; the frame structure of the GTK field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0210] In one embodiment, the third LAN extended authentication frame further includes: an IGTK information field, a BIGTK information field, an RSNE information field, and an RSNXE information field;

[0211] The frame structure of the IGTK information field, the BIGTK information field, the RSNE field, and the RSNXE information field includes at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

[0212] In one embodiment, when an operation other than a four-way handshake occurs, the data transmission apparatus applied to the second network device further includes:

[0213] The transmitter is further configured to send first key information on the new link to the first multi-link device; wherein the first key information at least includes link identifier information.

[0214] The data transmission device provided in this embodiment is configured to implement the data transmission method applied to the second network device in the embodiment shown in FIG15 . The implementation principle and technical effects of the data transmission device provided in this embodiment are similar and will not be described in detail here.

[0215] In one embodiment, Figure 26 is a schematic diagram of the structure of a communication device provided by an embodiment of the present application. As shown in Figure 26, the device provided by the present application includes: a processor 810, a memory 820, and a communication interface 830. The number of processors 810 in the device can be one or more, and Figure 26 uses one processor 810 as an example. The number of memories 820 in the device can be one or more, and Figure 26 uses one memory 820 as an example. The processor 810, memory 820, and communication interface 830 of the device can be connected via a bus or other means, and Figure 26 uses a bus connection as an example. In this embodiment, the device can be a resource management component.

[0216] The memory 820, as a computer-readable storage medium, can be configured to store software programs, computer executable programs, and modules, such as program instructions / modules corresponding to the device of any embodiment of the present application (for example, the receiver 510 and the forwarder 520 in the data transmission device applied to the first network device). The memory 820 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created based on the use of the device, etc. In addition, the memory 820 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 820 may further include a memory remotely located relative to the processor 810, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. Among them, the communication interface 830 is used for communication interaction between multiple communication devices.

[0217] In the case where the communication device is a first network device, the device provided above can be configured to execute the data transmission method applied to the first network device provided in any of the above embodiments, and have corresponding functions and effects.

[0218] In the case where the communication device is a first multi-link device, the device provided above can be configured to execute the data transmission method applied to the first multi-link device provided in any of the above embodiments, and have corresponding functions and effects.

[0219] In the case where the communication device is a second network device, the above-provided device can be configured to execute the data transmission method applied to the second network device provided in any of the above-mentioned embodiments, and have corresponding functions and effects.

[0220] An embodiment of the present application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a data transmission method applied to a first network device. The method includes: receiving a first authentication frame sent by a first multi-link device; and forwarding the first authentication frame to a second network device if the first authentication frame includes an authentication identifier.

[0221] An embodiment of the present application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a data transmission method applied to a first multi-link device. The method includes: sending a first authentication frame to a first network device, so that when the first authentication frame includes an authentication identifier, the first authentication frame is forwarded to a second network device by the first network device.

[0222] An embodiment of the present application also provides a storage medium containing computer-executable instructions. When the computer-executable instructions are executed by a computer processor, they are used to execute a data transmission method applied to a second network device. The method includes: receiving a first authentication frame forwarded by a first network device; wherein the first authentication frame includes an authentication identifier.

[0223] It will be appreciated by those skilled in the art that the term user equipment encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a car-mounted mobile station.

[0224] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

[0225] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0226] The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions. A computer program may be stored on a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (digital versatile discs (DVD) or compact disks (CD)), etc. Computer-readable media may include non-transient storage media. A data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and a processor based on a multi-core processor architecture.

[0227] The above are merely preferred embodiments of the present application and are not intended to limit the present application. Those skilled in the art will readily appreciate that various modifications and variations are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A data transmission method, applied to a first network device, comprising: Receiving a first authentication frame sent by a first multi-link device; In a case where the first authentication frame includes an authentication identifier, the first authentication frame is forwarded to the second network device.

2. The method according to claim 1, wherein: When the first authentication frame does not include the authentication identifier, the first authentication frame is directly processed.

3. The method according to claim 1, further comprising: receiving a second authentication frame including an authentication identifier sent by the second network device; The second authentication frame is forwarded to the first multi-link device.

4. The method according to claim 1, further comprising: Parsing the first authentication frame to obtain a corresponding first authentication submission message or a first authentication confirmation message; In a case where the first authentication frame includes an authentication identifier, the first authentication submission message or the first authentication confirmation message is forwarded to the second network device.

5. The method according to claim 4, further comprising: Receiving a second authentication submission message or a second authentication confirmation message sent by the second network device; Combining the received authentication identifier or the authentication identifier generated by itself with the second authentication submission message or the second authentication confirmation message into a corresponding second authentication frame; The second authentication frame is forwarded to the first multi-link device.

6. The method according to any one of claims 1 to 5, wherein: The authentication identifier includes one of the following: a media access control MAC address of the first network device; a MAC address of the second network device; or roaming capability indication information.

7. The method according to claim 1, further comprising: Receiving a first LAN extended authentication frame sent by the second network device; wherein the first LAN extended authentication frame carries at least a MAC address of the second network device; The first LAN extended authentication frame is forwarded to the first multi-link device.

8. The method according to claim 7, further comprising: receiving a second LAN extension authentication frame sent by the first multi-link device; wherein the second LAN extension authentication frame carries at least link identifier information consisting of a first network device identifier and a link identifier; The second LAN extended authentication frame is forwarded to the second network device.

9. The method according to claim 8, wherein: The first network device identifier includes at least one of the following: a MAC address of the first network device; and a first network device index.

10. The method according to claim 8, further comprising: Receiving a third LAN extended authentication frame sent by the second network device; wherein the third LAN extended authentication frame at least includes the first network device identifier, the link identifier, and a group temporary key GTK on the link; The third LAN extension authentication frame is forwarded to the first multi-link device.

11. The method according to claim 10, wherein: The third LAN extended authentication frame further includes: a GTK field; the frame structure of the GTK field includes at least a first device identifier field, which is used to indicate the first network device identifier corresponding to the third LAN extended authentication frame.

12. The method according to claim 10, wherein: The third LAN extended authentication frame also includes: an integrity group temporary key IGTK information field, a beacon frame integrity group temporary key BIGTK information field, a robust security network element RSNE information field, and an extended robust security network element RSNXE information field; Among them, the frame structure of the IGTK information field, the BIGTK information field, the RSNE field and the RSNXE information field includes at least the first device identifier field, which is used to indicate the first network device identifier corresponding to the third LAN extended authentication frame.

13. A data transmission method, applied to a first multi-link device, comprising: A first authentication frame is sent to a first network device, so that the first authentication frame is forwarded to a second network device through the first network device when the first authentication frame includes an authentication identifier.

14. The method according to claim 13, further comprising: Receive a first LAN extended authentication frame forwarded by the first network device; wherein the first LAN extended authentication frame carries at least a media access control MAC address of the second network device.

15. The method according to claim 14, further comprising: A second LAN extension authentication frame is sent to the first network device; wherein the second LAN extension authentication frame carries at least link identifier information consisting of the first network device identifier and the link identifier.

16. The method according to claim 15, further comprising: Receive a third LAN extension authentication frame forwarded by the first network device; wherein the third LAN extension authentication frame at least includes the first network device identifier, the link identifier, and a group temporary key on the link.

17. The method according to claim 13, in the case where an operation other than a four-way handshake occurs, the method further comprises: Receive first key information on a new link sent by the second network device; wherein the first key information at least includes link identifier information.

18. A data transmission method, applied to a second network device, comprising: A first authentication frame forwarded by a first network device is received; wherein the first authentication frame includes an authentication identifier.

19. The method according to claim 18, further comprising: A first LAN extended authentication frame is sent to the first network device; wherein the first LAN extended authentication frame carries at least a media access control MAC address of the second network device.

20. The method according to claim 19, further comprising: Receive a second LAN extension authentication frame forwarded by the first network device; wherein the second LAN extension authentication frame carries at least link identifier information consisting of a first network device identifier and a link identifier.

21. The method according to claim 20, further comprising: Sending a third local area network extension authentication frame to the first network device; wherein the third local area network extension authentication frame at least includes the first network device identifier, the link identifier, and a group temporary key on the link.

22. The method according to claim 18, in the case where an operation other than a four-way handshake occurs, the method further comprises: Sending first key information on a new link to a first multi-link device; wherein the first key information at least includes link identifier information.

23. A communication device comprising: memory, and at least one processor; The memory is configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the method as described in any one of claims 1-12, 13-17 or 18-22.

24. A storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 12, 13 to 17 or 18 to 22.

Images