Data transmission method and device and storage medium

Abstract

The invention provides a data transmission method and device and a storage medium. The data transmission method applied to a first network device comprises the following steps: receiving a first authentication frame sent by a first multi-link device; and forwarding the first authentication frame to second network equipment under the condition that the first authentication frame comprises an authentication identifier.

Description

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. The authentication request frames and other key generation related frames (such as EAPOL frames) sent using the Wi-Fi 7 protocol need to be processed in the high Media Access Control (high MAC) layer in 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 current technology to identify whether the non-AP MLD supports the multi-connection method across the EHT AP MLD defined by Wi-Fi 8. Therefore, the EHT AP MLD cannot know whether to forward the received multi-link authentication request frame to the high MAC of the UHR AP MLD for processing or to process it by itself. Summary of the invention

[0003] 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 prior 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.

[0004] The embodiment of the present application provides a data transmission method, which is applied to a first network device, including:

[0005] Receiving a first authentication frame sent by a first multi-link device;

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

[0007] The embodiment of the present application provides a data transmission method, which is applied to a first multi-link device, including:

[0008] 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.

[0009] The embodiment of the present application provides a data transmission method, which is applied to a second network device, including:

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

[0011] An embodiment of the present application provides a communication device, including: a memory, and one or more processors;

[0012] The memory is configured to store one or more programs;

[0013] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

[0014] An embodiment of the present application provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any of the above embodiments is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a schematic diagram of the implementation of a multi-link connection establishment process provided by the prior art;

[0016] Figure 2 It is a schematic diagram of the implementation of the interaction process of an SAE multi-link authentication method provided by the prior art;

[0017] Figure 3 It is a schematic diagram of the interaction of a four-way handshake process provided by the prior art;

[0018] Figure 4 It is a format configuration diagram of MLO Link KDE provided by the prior art;

[0019] Figure 5 It is a format configuration diagram of MLO GTK KDE provided by the prior art;

[0020] Figure 6 It is a format configuration diagram of IGTK KDE provided by the prior art;

[0021] Figure 7 It is a format configuration diagram of MLO BIGTK provided by the prior art;

[0022] Figure 8It is a configuration diagram of a UHR AP MLD architecture of a centralized UHR upper MAC provided by the prior art;

[0023] Fig. 9 It is a configuration diagram of a connection model before roaming provided by the prior art;

[0024] Fig.10 It is a configuration diagram of a roaming connection model provided by the prior art;

[0025] Fig.11 It is a configuration diagram of a connection model after roaming provided by the prior art;

[0026] Fig.12 It is a UHR AP MLD network architecture diagram provided by the prior art;

[0027] Fig.13 is a flow chart of a data transmission method provided in an embodiment of the present application;

[0028] Fig.14 is a flow chart of another data transmission method provided by an embodiment of the present application;

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

[0030] Fig.16 This is a schematic diagram of interaction of multi-link authentication of multiple EHT AP MLDs provided in an embodiment of the present application;

[0031] Fig.17 is a flowchart of a process of an EHT AP MLD receiving a first authentication frame provided by an embodiment of the present application;

[0032] Fig.18 This is a schematic diagram of an interaction of a multi-link four-way handshake of multiple EHT AP MLDs provided in an embodiment of the present application;

[0033] Fig.19 It is a format configuration diagram of an MLO Link KDE provided in an embodiment of the present application;

[0034] Fig. 20 It is a schematic diagram of a format configuration of MLO GTK KDE provided in an embodiment of the present application;

[0035] Fig.21 It is a format configuration diagram of MLO IGTK KDE provided in an embodiment of the present application;

[0036] Fig. 22It is a format configuration diagram of MLO BIGTK KDE provided in an embodiment of the present application;

[0037] Fig.23 is a structural block diagram of a data transmission device provided in an embodiment of the present application;

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

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

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

[0041] The following will describe the embodiments of the present application in conjunction with the accompanying drawings. The following will describe the present application in conjunction with the accompanying drawings of the embodiments, and the examples cited are only used to explain the present application and are not used to limit the scope of the present application.

[0042] In the Wi-Fi 7 protocol, Multi-Link Operation (MLO) technology is introduced. Multi-Link Device (MLD) includes network devices (AP MLD for short) and terminal devices (non-APMLD for short). In addition, Multi-Link Device can transmit data on multiple links simultaneously, which improves the data transmission throughput and reduces the data transmission delay.

[0043] After a 4-way handshake on a link, the AP MLD and non-AP MLD generate a temporary pairwise transmission key (PTK) at the MLO level and a group temporary key (GTK) at the link level, which are used to encrypt and decrypt the transmitted unicast data frames and anchor data frames, respectively, to ensure the security of data transmission. For example, Figure 1 It is a schematic diagram of the implementation of a multi-link connection establishment process provided by the prior art, such as Figure 1 As shown in the figure, both AP MLD and non-AP MLD include three links working at 2.4 GHz, 5 GHz and 6 GHz. APMLD and non-AP MLD complete the authentication, connection and four-way handshake process on the 2.4 GHz link. After establishing the multi-link connection, data can be transmitted on the three links (Link1, Link2 and Link3).

[0044] In the multi-link authentication process, the SAE protocol may be used to interact with relevant information. The messages of the SAE protocol include: a commit message and a confirm message. Figure 2 FIG. 1 is a schematic diagram of an implementation of the SAE multi-link authentication interaction process provided by the prior art. Figure 2 The implementation process is described as follows:

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

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

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

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

[0049] Step 3: On the Non-AP MLD and AP MLD, the key element P is generated according to a certain algorithm using the locally stored shared key information, supplicant MAC address, and Authenticator MAC address.

[0050] Step 4: At the Non-AP MLD end, use the secret key elements P, S(ap), E(ap) and the local random number r(sta) to generate K1 according to a certain secret key algorithm.

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

[0052] Step 6: On the Non-AP MLD side, K3 is generated using K1, and a confirm message (Csta) is generated using K3, S(ap), E(ap), S(sta), and E(sta) according to a certain secret key algorithm, and sent to the AP MLD using an Authentication frame.

[0053] Step 7: At the AP MLD end, K4 is generated using K2, and a confirm message (Cap) is generated using K4, S(ap), E(ap), S(sta), and E(sta) according to a certain secret key algorithm. (Cap) matches (Csta), and if they are the same, the Authentication frame is used to send Cap to the non-AP MLD.

[0054] Step 8: At the Non-AP MLD end, Csta is matched with the received Cap. If they are the same, it is proved that a local key K1=K2 is generated, and K1 / K2 is used as a pairwise master key (PMK).

[0055] Figure 3 This is a schematic diagram of the interaction of a four-way handshake process provided by the prior art. After completing the interaction of the association request frame and the response frame, the AP MLD sends a data frame containing an Extensible Authentication Protocol over LANs (EAPOL)-KEY message to the non-AP MLD on an associated link to start the four-way handshake. Figure 3 As shown, the implementation process of the four-way handshake is as follows:

[0056] Step 1: AP MLD sends the first EAPOL-KEY frame (EAPOL-1 for short) to non-AP MLD, which contains the authenticator MAC address and a random number (A-nonse) generated by the authenticator.

[0057] Step 2: The non-AP MLD sends the second EAPOL-KEY frame (EAPOL-2 for short) to the AP MLD, which includes the supplicant MAC address, the random number (S-nonse) generated by the supplicant, and the RSN and RSNXE information of each link requested by the non-AP MLD. Figure 4 This is a schematic diagram of the format configuration of an MLO Link KDE provided by the prior art. Figure 4 As shown, the MLO Link KDE field includes at least: a robust security network element (Robust Security Network Element, RSNE) and an extended robust security network element (Robust Security Network eXtension Element, RSNXE).

[0058] Step 3: AP MLD sends the third EAPOL-KEY frame (EAPOL-3 for short) to the non-AP MLD, which includes GTK information, IGTK information, BIGTK information, RSN of the requested link on the AP MLD side, RSNXE information, and integrity check information. Figure 5 It is a schematic diagram of the format configuration of MLO GTK KDE provided by the prior art, such as Figure 5 As shown, the GTK KDE field includes at least a LinkID field. Figure 6 This is a schematic diagram of an IGTK KDE format configuration provided by the prior art. Figure 6 As shown, the IGTKKDE field includes at least a Link ID field and an IGTK field. Figure 7 This is a schematic diagram of the format configuration of MLO BIGTK provided by the prior art. Figure 7 As shown, the BIGTK KDE field includes at least a Link ID field and a BIGTK field.

[0059] Step 4: The Non-AP MLD sends the fourth EAPOL-KEY frame (EAPOL-4 for short) to the AP MLD, which includes information for integrity verification.

[0060] In the Wi-Fi 8 protocol, it is proposed that UHR AP MLD can be deployed in different locations for the subordinate APs of the same UHR AP MLD to solve the latency problem caused by roaming on the device side. At the same time, the channel utilization problem can be solved through the collaboration of multiple subordinate APs in the same UHR AP MLD.

[0061] A centralized UHR AP MLD architecture is provided in the seamless roaming solution under the non-parallel AP MLD architecture. Figure 8 FIG. 1 is a configuration diagram of a centralized UHR upper MAC UHR AP MLD architecture provided by the prior art. Figure 8 As shown, 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. UHR non-AP MLD can establish a link connection with the Low MAC of any node without switching the connected network, solving the data transmission delay problem caused by network switching.

[0062] exist Figure 8 Based on the framework of , a whole model of the roaming process is provided, which includes three stages: before roaming, during roaming and after roaming. Fig. 9It is a configuration diagram of a connection model before roaming provided by the prior art; Fig.10 It is a configuration diagram of a roaming connection model provided by the prior art; Fig.11 FIG. 1 is a configuration diagram of a connection model after roaming provided by the prior art. Fig. 9 As shown in Figure 2, before roaming, a non-AP MLD selects a target AP Group and a target link (link4, link5); Fig.10 As shown in FIG. 1 , during the roaming process, the non-AP MLD disconnects a link (AP1) with AP group 1 and establishes a connection with AP Group 2 (AP4), and then repeats the process, disconnects a link (AP2) with AP group 1 and establishes a connection with AP Group 2 (AP5), and finally completes the roaming process. Fig.11 shown.

[0063] Fig.12 This is a UHR AP MLD network architecture diagram provided by the prior art. Fig.12 As shown in the figure, under the UHR AP MLD architecture, the multi-link authentication and key generation process across EHT AP MLD has the following problems:

[0064] 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 frames 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 EHTAP 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-connection mode across EHT AP MLD defined by Wi-Fi8. 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.

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

[0066] (Third, during the four-way handshake process of the initial connection, the UHR AP MLD needs to send the GTK, IGTK, and BIGTK of each Link that establishes multiple connections to the non-AP MLD. However, since each EHT AP MLD has a separate number (Link ID) for the attached Link, there may be a situation where multiple EHT AP MLDs have multiple Link connections with the same Link ID. The Non-AP MLD cannot distinguish the KEY information of different Links through the existing Link ID, and thus cannot decrypt and verify the integrity of the multicast message transmitted on the corresponding link.

[0067] Fourth, during roaming, the UHR AP MLD needs to send the GTK, IGTK, and BIGTK of the newly established multi-connected Link to the non-AP MLD, and release the resources corresponding to the dismantled Link in a timely manner. However, since each EHT AP MLD numbers the attached Links separately, and the Link number range is 0-14 or 0-15, there are scenarios where two EHT AP MLDs contain the same LinkID. The UHR AP MLD cannot confirm which EHT AP MLD has the multicast-related key of the Link through the Link ID of the 802.11be protocol.

[0068] 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, a UHR non-AP MLD or an EHT non-AP MLD).

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

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

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

[0072] In an embodiment, the authentication identifier is used to characterize whether the first authentication frame is forwarded to the second network device, and can also be used to characterize 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, when the first authentication frame does not contain the authentication identifier, the first authentication frame is directly processed. When the first authentication frame sent by the first multi-link device does not contain the authentication identifier, the first authentication frame is directly parsed and processed by the first network device.

[0073] 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; and then directly forwards the second authentication frame including the authentication identifier to the first multi-link device via the first network device.

[0074] 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 a first authentication confirmation message; and forwarding the first authentication submission message or the first authentication confirmation message to the second network device when the first authentication frame includes an authentication identifier. 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 a first authentication confirmation message, and 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.

[0075] 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 authentication identifier generated by itself 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 the 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 the 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.

[0076] 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.

[0077] 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; roaming capability indication information. The roaming capability indication information is used to indicate whether the UHR roaming capability is available. In one example, when the roaming capability indication information is 1, the first authentication frame is directly forwarded to the second network device through the first network device, and the second network device processes the first authentication frame; when the roaming capability indication information is 0, the first authentication frame can be processed by the first network device.

[0078] In one embodiment, the data transmission method applied to the first network device also 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; 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 a first LAN extended authentication frame, and sends the first LAN extended authentication frame to the first network device via a return link, and 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.

[0079] In one embodiment, the data transmission method applied to the first network device also 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 composed of the first network device identifier and the link identifier; 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 return link. In one example, the second LAN extended authentication frame contains at least link identifier information composed of the first network device identifier and the link identifier, so as to accurately distinguish information transmitted on different links on different first network devices.

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

[0081] In one embodiment, the data transmission method applied to the first network device further includes: 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 the group temporary key (GTK) on the link; forwarding the third LAN extended authentication frame to the first multi-link device. The second network device generates a third LAN extended authentication frame, and sends the third LAN extended authentication frame to the first network device via a return link, and includes at least the first network device identifier, the link identifier, and the group temporary key on the link in the third LAN extended authentication frame, so that the second network device can accurately confirm on which first network device the link key is to be verified through the link identifier.

[0082] 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 can send the third LAN extended authentication frame carrying at least 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 can decrypt and perform integrity verification on the message transmitted on the corresponding link.

[0083] 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;

[0084] 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 of 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 can decrypt and verify the integrity of the message transmitted on the corresponding link.

[0085] In one embodiment, Fig.14 is a flow chart of another data transmission method provided by an embodiment of the present application. This embodiment can be executed by the first multi-link device. Fig.14 As shown, this embodiment includes: S210.

[0086] 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.

[0087] 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.

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

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

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

[0091] 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.

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

[0093] 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, a link identifier, and a group temporary key on the link.

[0094] 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.

[0095] 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.

[0096] 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;

[0097] 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.

[0098] 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:

[0099] Receive the first key information on the new link sent by the second network device; wherein the first key information includes at least link identifier information. The first key information refers to GTK, IGTK, BIGTK information. In the case where the first multi-link device roams, for example, dynamically adding a link or switching a link, 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 can be a link identifier across multi-link devices.

[0100] It should be noted that, for explanations 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, see the description of the corresponding parameters applied to the first network device above, which will not be repeated here.

[0101] In one embodiment, Fig.15 1 is a flow chart of another data transmission method provided in an embodiment of the present application. This embodiment can be executed by the second network device. Fig.15 As shown, this embodiment includes: S310.

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

[0103] 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.

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

[0105] 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.

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

[0107] 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.

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

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

[0110] 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.

[0111] 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.

[0112] 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;

[0113] 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.

[0114] 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:

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

[0116] It should be noted that, for explanations 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, see the description of the corresponding parameters applied to the first network device or the first multi-link device, which will not be repeated here.

[0117] 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 an UHR AP MLD, and the first multi-link device as a non-AP MLD as an example.

[0118] Each UHR AP MLD is composed of a UHR upper MAC (including an authenticator running thereon) and multiple EHT AP MLDs at different physical locations. The EHT AP MLD establishes a backhaul link with the UHR upper MAC in a wired or wireless manner.

[0119] On this basis, the embodiment of the present application proposes a multi-EHT AP MLD multi-link authentication and four-way handshake scheme under a UHR AP MLD architecture. This scheme can not only realize the establishment of multi-link connections between non-AP MLD and an EHT AP MLD under UHR AP MLD, but also realize the establishment of multiple link connections between non-AP MLD and multiple EHT AP MLDs under UHR AP MLD.

[0120] In one embodiment, Fig.16 This is an interactive diagram of multi-link authentication of multiple EHT AP MLDs provided in an embodiment of the present application. In this embodiment, 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 HUR 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, the multi-link authentication process of multiple EHT AP MLDs is described. Fig.16 As shown, the multi-link connection authentication process of multiple EHT AP MLDs is as follows:

[0121] 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).

[0122] 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.

[0123] Step 3: 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 it to EHT AP MLD1 through a backhaul link.

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

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

[0126] For the above Fig.16 The steps shown are further explained as follows:

[0127] 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.

[0128] In some application instances, 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 in EHT AP MLD1, and sends it to the non-AP MLD from the first link.

[0129] In some application examples, EHT AP MLD1 receives an authentication frame including 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 it, and sends it to the non-AP MLD from the first link. This process may involve changes to the protocol frame header.

[0130] 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 the frame will not be forwarded to the UHR AP MLD.

[0131] In one example, Fig.17 FIG. 1 is a flowchart of a processing flow of an EHT AP MLD for a received first authentication frame provided by an embodiment of the present application. Fig.17 As shown, the processing process of the EHT AP MLD for the received first authentication frame includes:

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

[0133] S420: Whether the first authentication frame contains an authentication identifier, if so, execute S430; if not, execute S440.

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

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

[0136] In one example, Fig.18 This is a schematic diagram of the interaction of a multi-link four-way handshake of multiple EHT AP MLDs provided in an embodiment of the present application. In the embodiment, taking the communication on a 2.4GHz link, 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, and the fourth LAN extended authentication frame is an EAPOL-4 as an example, the interaction process of the multi-link four-way handshake of multiple EHT AP MLDs is described. Fig.18 As shown, the implementation process of multi-EHT AP MLD multi-link 4-way handshake is described as follows:

[0137] 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) through a backhaul link. The EAPOL-1 frame at least includes an authenticator MAC and an A-nonce.

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

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

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

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

[0142] Step 5: UHR AP MLD generates an EAPOL-3 frame and sends it to EHT AP MLD1 through the backhaul link. The EAPOL-3 frame contains at least multiple connection link identifiers and their GTK information, as well as RSNE, RSNXE information and MIC information corresponding to the UHR AP MLD-side link.

[0143] Step 6: EHT AP MLD1 may send the EAPOL-3 frame to the non-AP MLD via the 2.4 GHz associated link.

[0144] 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.

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

[0146] For the above Fig.18 The steps shown are further explained as follows:

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

[0148] In some application instances, the link identifier information is identified by 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).

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

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

[0151] In some application examples, EAPOL-3 may also include IGTK and BIGTK information, whose formats are as follows: Fig. 22 shown. Fig.21 This is a schematic diagram of the format configuration of MLO IGTK KDE provided in an embodiment of the present application. Fig.21 As shown, the IGTK KDE format at least includes the first network device identifier (ie, MLD index). Fig. 22 FIG. 1 is a schematic diagram of a format configuration of MLO BIGTK KDE provided in an embodiment of the present application. Fig. 22 As shown, the MLO BIGTK format at least includes a first network device identifier (ie, MLD index).

[0152] In some application instances, in roaming scenarios, such as 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 link identifier across the MLDs and the GTK, IGTK, and BIGTK information corresponding to the link.

[0153] In one embodiment, Fig.23 1 is a structural block diagram of a data transmission device provided in an embodiment of the present application. This embodiment is applied to a first network device. Fig.23 As shown, the data transmission device in this embodiment includes: a receiver 510 and a repeater 520 .

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

[0155] 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.

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

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

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

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

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

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

[0162] 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.

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

[0164] 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;

[0165] 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;

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

[0167] 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.

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

[0169] 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;

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

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

[0172] The receiver 510 is further configured to receive 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 the first network device identifier and the link identifier;

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

[0174] 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.

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

[0176] 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 at least includes the first network device identifier, the link identifier, and the group temporary key on the link;

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

[0178] 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 local area network extended authentication frame.

[0179] 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;

[0180] 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 local area network extended authentication frame.

[0181] The data transmission device provided in this embodiment is configured to implement Fig.13 The data transmission method applied to the first network device in the illustrated embodiment is similar to the implementation principle and technical effect of the data transmission device provided in this embodiment, and will not be described in detail here.

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

[0183] 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 through the first network device.

[0184] 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.

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

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

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

[0188] 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.

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

[0190] 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, a link identifier, and a group temporary key on the link.

[0191] 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.

[0192] 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.

[0193] 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;

[0194] 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.

[0195] 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:

[0196] 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.

[0197] The data transmission device provided in this embodiment is configured to implement Fig.14 The data transmission method applied to the first multi-link device in the illustrated embodiment is similar to the data transmission device provided in this embodiment in terms of implementation principle and technical effect, which will not be described in detail herein.

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

[0199] 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.

[0200] 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.

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

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

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

[0204] 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.

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

[0206] The transmitter is further configured to send a third local area network extended authentication frame to the first network device; 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.

[0207] 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.

[0208] 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.

[0209] 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;

[0210] 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.

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

[0212] 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.

[0213] The data transmission device provided in this embodiment is configured to implement Fig.15 The data transmission method applied to the second network device in the illustrated embodiment is similar to the implementation principle and technical effect of the data transmission device provided in this embodiment, and will not be described in detail here.

[0214] In one embodiment, Fig.26 Schematic diagram of the structure of a communication device provided in an embodiment of the present application. Fig.26 As shown, 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. Fig.26 In the example, a processor 810 is used. The number of memories 820 in the device may be one or more. Fig.26 A memory 820 is taken as an example. The processor 810, the memory 820 and the communication interface 830 of the device can be connected via a bus or other means. Fig.26 In the embodiment, the bus connection is taken as an example. In this embodiment, the device may be a resource management component.

[0215] The memory 820, as a computer-readable storage medium, may 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 repeater 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, an application required for at least one function; the data storage area may store data created according to 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 arranged 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.

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

[0217] 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 has corresponding functions and effects.

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

[0219] The embodiment of the present application also provides a storage medium containing computer executable instructions, which are used to execute a data transmission method applied to a first network device when executed by a computer processor, the method comprising: receiving a first authentication frame sent by a first multi-link device; and forwarding the first authentication frame to a second network device when the first authentication frame contains an authentication identifier. .

[0220] 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 first multi-link device. The method includes: sending a first authentication frame to a first network device, so that when the first authentication frame contains an authentication identifier, the first authentication frame is forwarded to a second network device through the first network device.

[0221] 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.

[0222] 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.

[0223] In general, various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can 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.

[0224] 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.

[0225] 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 have 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 memory 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 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 (FGPAs) and a processor based on a multi-core processor architecture.

[0226] The above are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A data transmission method, characterized in that: 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, characterized in that 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, characterized in that The method further comprises: receiving a second authentication frame including an authentication identifier sent by a second network device; Forwarding the second authentication frame to the first multi-link device.

4. The method according to claim 1, wherein The method further comprises: 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, characterized in that The method further comprises: 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 into a corresponding second authentication frame; Forwarding the second authentication frame to the first multi-link device.

6. The method according to any one of claims 1 to 5, characterized in that 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, characterized in that The method further comprises: Receive a first LAN extended authentication frame sent by a second network device; wherein the first LAN extended authentication frame carries at least a MAC address of the second network device; Forwarding the first LAN extended authentication frame to the first multi-link device.

8. The method according to claim 7, characterized in that The method further comprises: 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 a first network device identifier and a link identifier; Forward the second LAN extended authentication frame to the second network device.

9. The method according to claim 8, characterized in that 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, characterized in that The method further comprises: Receiving 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 GTK on the link; Forwarding the third LAN extended authentication frame to the first multi-link device.

11. The method according to claim 10, characterized in that 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, characterized in that 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; The frame structures of the IGTK information field, the BIGTK information field, the RSNE field, and the RSNXE information field include at least a first device identifier field for indicating the first network device identifier corresponding to the third LAN extended authentication frame.

13. A data transmission method, characterized in that: Applicable 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 via the first network device if the first authentication frame includes an authentication identifier.

14. The method according to claim 13, characterized in that The method further comprises: 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.

15. The method according to claim 14, characterized in that The method further comprises: 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.

16. The method according to claim 15, characterized in that The method further comprises: A third LAN extended authentication frame forwarded by the first network device is received; 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.

17. The method according to claim 13, wherein In the event that an operation other than a four-way handshake occurs, the method further includes: 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, characterized in that: Applicable to the second network device, including: 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, characterized in that The method further comprises: 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.

20. The method according to claim 19, characterized in that The method further comprises: Receive a second LAN extended authentication frame forwarded by 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.

21. The method according to claim 20, characterized in that The method further comprises: 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.

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

23. A communication device, characterized in that: include: memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 12, 13 to 17, or 18 to 22.

24. A storage medium, characterized in that The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 12, 13 to 17, or 18 to 22 is implemented.

Images