Communication methods, device, and storage medium

Abstract

The present application belongs to the technical field of communications. Disclosed are communication methods, a device and a storage medium. A method comprises: a multi-link terminal device acquiring a pre-configured terminal identifier and / or at least one link identifier; and the multi-link terminal device sending to a multi-link network device a first frame which contains the terminal identifier and / or the at least one link identifier, so that the multi-link network device identifies the multi-link terminal device and / or a link according to the terminal identifier and / or the at least one link identifier.

Description

Communication method, device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the Chinese patent application with application number 2023109210447 and application date July 24, 2023, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference. Technical Field

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

[0004] During the communication process, terminal devices usually use a unique fixed Media Access Control Address (MAC) address to establish a connection with network devices. Identification and authentication technologies based on fixed MAC addresses of devices have been widely used in the field of wireless transmission. However, the use of fixed MAC addresses can easily lead to third-party devices using MAC address sniffing technology to track and locate the connection between terminal devices and network devices. To solve this problem, related technologies allow users to use random MAC addresses (RMA, Random MAC address) before the terminal device accesses the network device. However, the random MAC address technology of terminal devices has caused the device MAC address-related functions defined by the Wi-Fi Alliance (WFA) and the Wi-Fi Broadband Alliance (WBA) to fail, resulting in the network being unable to manage the device.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a communication method, device, and storage medium that can implement network management of devices and improve the security of the communication process.

[0007] In a first aspect, an embodiment of the present application provides a communication method, the method comprising:

[0008] The multi-link terminal device obtains a pre-configured terminal identifier and / or at least one link identifier;

[0009] The multi-link terminal device sends a first frame to a multi-link network device, where the first frame includes the terminal identifier and / or at least one link identifier, so that the multi-link network device identifies the multi-link terminal device and / or the link according to the terminal identifier and / or at least one link identifier.

[0010] In a second aspect, an embodiment of the present application provides a communication method, the method comprising:

[0011] The multi-link network device receives a first frame sent by a multi-link terminal device, where the first frame includes a terminal identifier and / or at least one link identifier;

[0012] The multi-link network device identifies the multi-link terminal device and the link according to the terminal identifier and / or at least one of the link identifiers.

[0013] In a third aspect, an embodiment of the present application provides an electronic device, including:

[0014] one or more processors;

[0015] A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement:

[0016] The communication method according to the first aspect; or

[0017] The communication method as described in the second aspect.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements:

[0019] The communication method according to the first aspect; or

[0020] The communication method as described in the second aspect.

[0021] The embodiment of the present application includes: a multi-link terminal device is pre-configured with a terminal identifier and / or at least one link identifier. When communication is required, the multi-link terminal device sends a first frame carrying the terminal identifier or / at least one link identifier to the multi-link network device. The multi-link network device identifies the multi-link terminal device and the link based on the terminal identifier or / at least one link identifier, thereby establishing a corresponding link with the multi-link terminal device, providing different network access services for the multi-link terminal device, and realizing a multi-link connection between the multi-link terminal device and the multi-link network device. The network corresponding to the multi-link network device can manage the multi-link terminal device and improve the security of the communication process. The embodiment of the present application enables the multi-link network device to identify the multi-link terminal device and the link through the setting of the terminal identifier and / or at least one link identifier, thereby realizing a multi-link connection between the multi-link terminal device and the multi-link network device. The multi-link network device can provide corresponding network access services to the multi-link terminal device based on the connection and manage it. In addition, the setting of the terminal identifier and the link identifier can reduce the sniffing positioning of third-party devices and improve the security of communication.

[0022] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become obvious from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only some embodiments of the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0024] FIG1 is a system architecture diagram of a communication method application system provided in an embodiment of the present application;

[0025] FIG2 is a flow chart of a communication method provided by an embodiment of the present application at a multi-link terminal device;

[0026] FIG3 is another flow chart of the communication method provided by an embodiment of the present application at a multi-link terminal device;

[0027] FIG4 is a schematic diagram of the structure of the first target field of the communication method provided in an embodiment of the present application;

[0028] FIG5 is another structural diagram of the first target field of the communication method provided in an embodiment of the present application;

[0029] FIG6 is a schematic diagram of the structure of a device identification control bitmap field of a communication method provided in an embodiment of the present application;

[0030] 7 is a schematic diagram of the structure of the device identification information field of the communication method provided in an embodiment of the present application;

[0031] FIG8 is a schematic structural diagram of the first frame and the fourth frame of the communication method provided in an embodiment of the present application;

[0032] FIG9 is a schematic structural diagram of a second target field of a communication method provided in an embodiment of the present application;

[0033] FIG10 is another structural diagram of the second target field of the communication method provided in an embodiment of the present application;

[0034] FIG11 is a schematic diagram of the structure of the IRM control bitmap field of the communication method provided in an embodiment of the present application;

[0035] 12 is a flow chart of generating a terminal identifier and / or at least one link identifier at a multi-link terminal device in a communication method according to an embodiment of the present application;

[0036] 13 is a schematic diagram of a multi-link terminal device communicating with a multi-link network device according to an embodiment of the present application;

[0037] 14 is another flowchart of generating a terminal identifier and / or at least one link identifier at a multi-link terminal device in a communication method provided in an embodiment of the present application;

[0038] 15 is another schematic diagram of the communication between a multi-link terminal device and a multi-link network device provided in an embodiment of the present application;

[0039] FIG16 is a step diagram of a communication method provided in an embodiment of the present application at a multi-link network device;

[0040] FIG17 is another flow chart of the communication method provided in an embodiment of the present application at a multi-link network device;

[0041] 18 is a flow chart of generating a terminal identifier and / or at least one link identifier at a multi-link network device in a communication method according to an embodiment of the present application;

[0042] 19 is another flow chart of generating a terminal identifier and / or at least one link identifier at a multi-link network device in a communication method according to an embodiment of the present application;

[0043] Figure 20 is a schematic diagram of an electronic device to which the communication method provided in an embodiment of the present application is applied. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0045] It should be noted that although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be performed in a different order than that shown in the flowcharts. The terms "first," "second," and the like in the specification, claims, and drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0046] It should also be understood that references to "one embodiment" or "some embodiments" described in the description of the embodiments of the present application mean that one or more embodiments of the embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Thus, the phrases "in one embodiment," "in some embodiments," "in some other embodiments," "in some other embodiments," etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0047] In the description of this application, “greater than”, “less than”, “exceed”, etc. are understood as not including the number itself, and “above”, “below”, “within”, etc. are understood as including the number itself. If there is a description of “first” or “second”, it is only used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features. It should be understood that the description of the orientation, such as up, down, front, back, left, right, etc., indicating the orientation or position relationship is based on the orientation or position relationship shown in the drawings, and is only for the convenience of describing this application and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on this application.

[0048] In the description of the embodiments of the present application, unless otherwise clearly defined, terms such as setting, installing, and connecting should be understood in a broad sense. Technical personnel in the relevant technical field can reasonably determine the specific meanings of the above terms in the embodiments of the present application based on the specific content of the technical solution.

[0049] During the communication process, terminal devices typically use a unique, fixed MAC address to establish a connection with network devices. Identification and authentication technologies based on fixed MAC addresses have been widely used in the field of wireless transmission. However, the use of fixed MAC addresses can easily lead to third-party devices using MAC address sniffing technology to track and locate the connection between terminal devices and network devices. For example, wireless network technology introduces multi-link operation (MLO) technology, which divides MAC addresses into link-level MAC addresses (Link MAC addresses) and MLD-level MAC addresses (Multi-link device MAC addresses). Based on the differences in the MAC address information carried, frames used for multi-link terminal device identification are generally divided into three categories: those carrying only link-level MAC addresses; those carrying both the current link-level MAC address and the MLD-level MAC address; and those carrying both the current link-level MAC address, other link-level MAC addresses, and the MLD-level MAC address. Third-party devices can track and locate the communication process based on the link-level MAC address and the MLD-level MAC address.

[0050] To address this issue, related technologies allow users to use a random MAC address (RMA) before connecting a terminal device to a network device. However, this random MAC address technology for terminal devices has caused the device MAC address-based functions defined by the Wi-Fi Alliance (WFA) and the Wi-Fi Broadband Alliance (WBA) to fail, making it impossible for the network to manage the device.

[0051] Based on this, the present application provides a communication method, device and storage medium. The communication method provided in the embodiment of the present application enables a multi-link network device to identify a multi-link terminal device and a link through the setting of a terminal identifier and / or at least one link identifier, thereby realizing a multi-link connection between a multi-link terminal device and a multi-link network device. The multi-link network device can provide corresponding network access services to the multi-link terminal device based on the connection and manage it. In addition, the setting of the terminal identifier and the link identifier can reduce the sniffing positioning of third-party devices and improve the security of communication.

[0052] The present application will be further described below with reference to the accompanying drawings.

[0053] 1 is a diagram of the system architecture of a communication method according to an embodiment of the present application, which includes a multi-link terminal device and a multi-link network device.

[0054] The multi-link network device is a device that receives the first frame sent by the multi-link terminal device and can identify the multi-link terminal device and the link based on the terminal identifier and / or at least one link identifier. The multi-link network device communicates with the multi-link terminal device in a wireless manner and exchanges data.

[0055] A multi-link network device, also known as a wireless access point, is a wireless network access device and the core device of a wireless local area network (WLAN). It converts a wired network into a wireless network, allowing multi-link end devices to connect wirelessly. Furthermore, it enables multiple end devices to connect simultaneously, providing high-speed and stable network services. A wireless network access device operates by converting wired network signals into wireless signals, which are then used to transmit data. In a wireless network, a wireless network access device acts as a relay station, receiving data from wireless devices and transmitting it to the wired network. Furthermore, a wireless network access device can receive data from the wired network, convert it into wireless signals, and transmit it to wireless devices.

[0056] A multi-link terminal device is a device that obtains a pre-configured terminal identifier and / or at least one link identifier and sends a first frame to a multi-link network device. The multi-link terminal device can communicate with the multi-link network device and exchange data, and multiple links can be established between the multi-link terminal device and the multi-link network device as needed.

[0057] It should be noted that both multi-link terminal devices and multi-link network devices include three links at 2.4 GHz, 5 GHz, and 6 GHz. Multi-link terminal devices and multi-link network devices can complete the authentication, connection, and four-way handshake processes on the 2.4 GHz link through the Association Request frame and the Association Response frame, thereby realizing multi-link connection, that is, being able to transmit data on the three links of 2.4 GHz, 5 GHz, and 6 GHz.

[0058] It should be noted that the multi-link terminal device and the multi-link network device can realize multi-link connection. The application system shown in FIG1 is only a schematic diagram. The multi-link connection between the multi-link terminal device and the multi-link network device includes at least one link connection.

[0059] It should be noted that the multi-link terminal device and the multi-link network device are just a general term. In the actual communication process, both the multi-link terminal device and the multi-link network device can be set to multiple.

[0060] The system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0061] Those skilled in the art will understand that the system architecture shown in FIG1 does not constitute a limitation on the embodiments of the present application, and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0062] In the system architecture shown in FIG1 , each unit can respectively call its stored communication program to execute the communication method.

[0063] Based on the structure of the above system architecture, various embodiments of a communication method of the present application are proposed.

[0064] 2, which is a flow chart of a communication method provided by an embodiment of the present application at a multi-link terminal device. The communication method provided by an embodiment of the present application includes but is not limited to the following steps:

[0065] Step S110: The multi-link terminal device obtains a pre-configured terminal identifier and / or at least one link identifier.

[0066] Step S120: The multi-link terminal device sends a first frame to the multi-link network device, where the first frame includes a terminal identifier and / or at least one link identifier, so that the multi-link network device identifies the multi-link terminal device and / or link based on the terminal identifier and / or at least one link identifier.

[0067] It should be noted that the multi-link terminal device obtains a pre-configured terminal identifier and / or at least one link identifier. The terminal identifier corresponds to the multi-link terminal device, and the link identifier corresponds one-to-one to the link. The multi-link terminal device sends a first frame to the multi-link network device. The first frame includes the terminal identifier and / or at least one link identifier. The multi-link network device identifies the multi-link terminal device and / or the link through the terminal identifier and / or at least one link identifier, thereby establishing a multi-link connection, that is, transmitting data on multiple links at the same time, and providing corresponding network access services to the multi-link terminal device based on the multi-link connection, and managing the multi-link terminal device. In addition, the setting of the terminal identifier and the link identifier can reduce the sniffing positioning of third-party devices and improve the security of communication.

[0068] In an exemplary embodiment, a multi-link network device identifies a multi-link terminal device and / or a link using a terminal identifier and / or at least one link identifier, and feeds back identification result information to the multi-link terminal device. If the multi-link terminal device and / or the link of the multi-link terminal device is successfully identified by the multi-link network device, the multi-link network device feeds back information to the multi-link terminal device. As a result, the multi-link terminal device can send a connection request to the multi-link network device, so that the multi-link network device and the multi-link terminal device establish a multi-link connection, i.e., transmit data simultaneously over multiple links. The establishment of the multi-link connection can provide corresponding network access services for the multi-link terminal device.

[0069] It should be noted that multi-link connections allow multi-link network devices and multi-link terminal devices to transmit data simultaneously on multiple links, thereby improving data transmission throughput, reducing data transmission latency, and thus improving communication efficiency.

[0070] It should be noted that the terminal identifier corresponds to the multi-link terminal device, and the multi-link network device can identify the multi-link terminal device based on the terminal identifier, and the link identifier corresponds one-to-one to the link that the multi-link terminal device can connect to. The multi-link network device can identify the corresponding link based on the link identifier, thereby establishing a connection with the multi-link terminal device.

[0071] It should be noted that in multi-link operation technology, MAC addresses are divided into link-level MAC addresses and MLD-level MAC addresses. A multi-link terminal device typically includes a unique MLD-level MAC address and at least one link-level MAC address. The MLD-level MAC address uniquely identifies a multi-link terminal device. Therefore, a multi-link terminal device corresponds to a link identifier, and a multi-link network device can identify the unique corresponding multi-link terminal device through the link identifier. In addition, each link-level MAC address of the same multi-link terminal device is different, but one of the link-level MAC addresses of the multi-link terminal device may be the same as the MLD-level MAC address. Therefore, the link identifiers corresponding to multiple links of the same link terminal device are different, and one of the link identifiers may also be the same as the terminal identifier. When the frame used for multi-link terminal device identification carries only the link-level MAC address, the first frame only needs to carry the link identifier. When the link identifier is the same as the terminal identifier, the first frame only needs to carry the terminal identifier or the link identifier. When the frame used for multi-link terminal device identification carries both the current link-level MAC address and the MLD-level MAC address, the first frame carries the terminal identifier and a link identifier. When a frame used for multi-link terminal device identification carries the MAC address of the current link level, MAC addresses of other link levels, and a MAC address of the MLD level at the same time, the first frame carries the terminal identifier and multiple link identifiers.

[0072] It should be noted that the terminal identifier and the link identifier can be configured through a multi-link terminal device or a multi-link network device.

[0073] It should be noted that the first frame is encrypted and transmitted between the multi-link terminal device and the multi-link network device. Therefore, the terminal identifier and link identifier carried by the first frame cannot be sniffed and tracked by third-party devices, thereby improving the security of communication transmission.

[0074] It should be noted that before the multi-link terminal device sends the first frame to the multi-link network device, the multi-link network device receives the terminal identifier and / or at least one link identifier sent from the multi-link terminal device, and saves the terminal identifier and / or at least one link identifier locally or in other multi-link network devices associated with the local area. The terminal identifier and link identifier correspond to those carried in the first frame, so that the multi-link network device can subsequently identify the terminal identifier and link identifier.

[0075] It should be noted that the first frame is a frame sent by the multi-link terminal device to the multi-link network device. The frame is usually used to request a connection with the multi-link network device, such as an association request frame in the Fast Initial Link Setup (FILS) mode.

[0076] It should be noted that the encrypted transmission of the first frame can be achieved through a key. Specifically, the multi-link terminal device and the multi-link network device generate a multi-link operation-level pairwise transmission key (PTK) and a link-level group temporary key (GTK) through a four-way handshake on a link. These are used to encrypt and decrypt the transmitted unicast data frames and anchor data frames, respectively, to ensure the security of data transmission.

[0077] It is understood that, with reference to FIG3 , the communication method provided in the embodiment of the present application further includes but is not limited to the following steps:

[0078] Step S130: The multi-link terminal device receives a fourth frame sent by the multi-link network device, where the fourth frame is a response frame to the first frame.

[0079] It should be noted that after receiving the first frame, the multi-link network device identifies the terminal identifier and link identifier, that is, determines whether the same terminal identifier and link identifier are stored locally or in the network corresponding to the multi-link network device. Based on the determination result, the device generates a fourth frame and sends the fourth frame to the multi-link terminal device. Therefore, the fourth frame is a response frame to the first frame. If the fourth frame indicates that the same terminal identifier and link identifier are stored locally or in a network associated with the multi-link network device, the multi-link terminal device establishes a multi-link connection with the multi-link network device and performs data transmission. Otherwise, the connection between the multi-link terminal device and the multi-link network device cannot be successfully established.

[0080] It can be understood that, referring to Figures 4 and 5, the first frame and / or the fourth frame contains a first target field, the terminal identifier contains a device identifier, the first target field includes a device identification information field, and the terminal identifier and / or at least one link identifier is located in the device identification information field.

[0081] It should be noted that the terminal identifier of the multi-link terminal device can be set to a device ID, which is the device ID of the multi-link terminal device. The multi-link network device can obtain the ID of the multi-link terminal device by identifying the device ID.

[0082] It should be noted that the link identifier may also be represented by a device identifier, and each link identifier is provided with a corresponding device identifier.

[0083] It should be noted that the first and fourth frames include a first destination field. The structure of the first destination field is shown in FIG4 or FIG5 . The first destination field includes a device identification information field (device ID info.), and a terminal identifier and / or at least one link identifier are set in the device identification information field. The device identification information field can include multiple different device identifiers. The number of octets in the device identification information field is variable, and its specific value can be set according to the number of terminal identifiers and link identifiers.

[0084] It can be understood that, referring to FIG. 4 and FIG. 5 , the first target field further includes a device identification recognition status field, and the device identification recognition status field is used to indicate whether the device identification of the multi-link terminal device is recognized.

[0085] It should be noted that the first target field also includes a device identification status field (Device ID Status), and the device identification status field is used to indicate whether the device identification of the multi-link terminal device is identified.

[0086] It should be noted that the device identification status field is set to 1 byte. When the device identification status field is 0, the device identification of the multi-link terminal device is not identified. When the device identification status field is 1, the device identification of the multi-link terminal device can be identified.

[0087] It should be noted that the fourth frame received by the multi-link terminal device is a response frame based on the first frame sent by the multi-link network device. When the multi-link network device can identify the terminal identifier of the multi-link terminal device, the device identifier identification status field is 1, and the multi-link network device and the multi-link terminal device can establish a connection. When the multi-link network device cannot identify the terminal identifier of the multi-link terminal device, the device identifier identification status field is 0, and the connection between the multi-link network device and the multi-link terminal device fails to be established.

[0088] It can be understood that, referring to FIG. 4 to FIG. 6 , the first target field further includes a device identification control bitmap field, and the device identification control bitmap field includes one or more of the following fields:

[0089] The device identification recognition status tag is used to indicate whether the first target field includes a device identification recognition status field.

[0090] The device identification tag is used to indicate whether the device identification information field contains the device identification.

[0091] Multiple link tags are used to indicate whether the device identification information field contains a corresponding link identifier.

[0092] The device identifier and link identifier share an indicator tag, which is used to indicate whether the device identifier and the link identifier have the same value.

[0093] It should be noted that the first target field also includes a device identification control bitmap field (Device ID control bitmap), which is compatible with the multi-link operation technology. The setting of the device identification control bitmap field provides a basis for the multi-link connection between the multi-link terminal device and the multi-link network device.

[0094] It should be noted that the device identification status tag (Device ID Status) is used to indicate whether the first target field contains the device identification status field. The device identification status tag occupies 1 bit. When the device identification status tag is 0, the first target field does not contain the device identification status field. When the device identification status tag is 1, the first target field contains the device identification status field.

[0095] It should be noted that the multi-link terminal device sends the first frame to the multi-link network device. Although the first frame contains a terminal identifier and / or at least one link identifier, the terminal identifier in the first frame is pre-configured, and the device identifier in the terminal identifier is the device identifier of the multi-link terminal device. Therefore, the first target field of the first frame does not include a device identifier identification field, and the device identifier identification status tag is correspondingly set to 0.

[0096] It should be noted that the fourth frame is a response frame to the first frame. After the multi-link network device identifies the multi-link terminal device based on the terminal identifier in the first frame, it generates a fourth frame and sends the fourth frame to the multi-link terminal device. Therefore, the first target field corresponding to the fourth frame contains the device identification recognition field, then the device identification recognition status tag is 1.

[0097] It should be noted that, referring to Figure 6, the multiple link labels are the first link label (1st.link ID), the second link label (2nd.link ID), and the third link label (3rd.link ID). Each link label corresponds to a corresponding link and can indicate whether the device identification information field contains the link identifier of the corresponding link. When the link label is 1, it indicates that the corresponding link identifier is included in the subsequent device identification information field. When the link label is 0, the device identification information field does not contain the corresponding link identifier.

[0098] It should be noted that the device identification control bitmap field shown in Figure 6 is configured with three link tags: a first link tag, a second link tag, and a third link tag, each of which occupies one bit. A multi-link terminal device and a multi-link network device both include three links: a first link, a second link, and a third link. The multi-link terminal device and the multi-link network device can connect via any one or more of these three links. The first link, the second link, and the third link are each configured with a corresponding link identifier. For the first frame, when multiple link tags are 1, it indicates that the multi-link terminal device wishes to establish a connection with the multi-link network device over the corresponding links. For example, when the first link tag and the second link tag in the first target field of the first frame are 1, and the third link tag is 0, the device identification information field only contains the link identifiers corresponding to the first and second links, indicating that the multi-link terminal device wishes to establish a connection with the multi-link device over the first and second links. For the fourth frame, the values ​​of the multiple link tags in the first target field correspond to those in the first frame. When the identification status field is 1, the device identifier of the multi-link terminal device can be recognized by the multi-link network device.

[0099] It should be noted that if the multi-link network device is successfully identified and the device identifier of the multi-link terminal device can be recognized by the multi-link network device, then the identification status field of the fourth frame is 1. Based on this, the multi-link terminal device can send a connection request to the multi-link network device so that the multi-link terminal device and the multi-link network device can establish a connection between the corresponding links and realize a multi-link connection.

[0100] It should be noted that the device identification control bitmap field in FIG6 is only an example. The number of link labels can be set to more or less. The number of link labels in the device identification control bitmap field is determined by the number of links of the multi-link terminal device and the multi-link network device.

[0101] It should be noted that the device identification control bitmap field contains a device identification and link identification sharing indicator tag, which occupies one bit and is used to identify whether the device identification and link identification have the same value. In multi-link operation technology, one of the link-level MAC addresses of a multi-link terminal device may be the same as the MLD-level MAC address. Therefore, the link identifiers corresponding to multiple links of the same link terminal device are different, but one of the link identifiers may also be the same as the terminal identifier. When the device identification and link identifier are the same, the device identification and link identification sharing indicator tag is 1, otherwise it is 0.

[0102] In one embodiment, the device identifier and link identifier sharing indicator are implicit. Specifically, the communication protocol stipulates that the terminal identifier and the link identifier are the same. Therefore, the first target field under the protocol does not need to set the device identifier and link identifier sharing indicator separately.

[0103] It should be noted that, referring to FIG. 6 , the device identification control bitmap field also includes a reserved tag (Reserved), which occupies 2 bits.

[0104] It can be understood that, referring to FIG. 7 , the device identification information field includes a length field and a device identification field.

[0105] It should be noted that the device identification information field includes a length field (length) and a device identification field (Device ID). The device identification field is used to store the device identification of the multi-link terminal device, and the length field is used to indicate the length of the device identification of the multi-link terminal device.

[0106] It can be understood that, referring to Figure 8, the first frame and the fourth frame include a media access control MAC header and a frame body respectively, the first target field is located in the MAC header or the frame body, and the first target field is a device identification element field or a device identification key data encapsulation field.

[0107] It should be noted that the first frame and the fourth frame include a media access control MAC header and a frame body, respectively, and the first target field is located in the frame body or the MAC header. The first target field is a device identification element field or a device identification key data encapsulation field.

[0108] It should be noted that when the terminal identifier and link identifier are the same, the terminal identifier is located in the Transmitter Address (TA) or Receiver Address (RA) field of the MAC header. When the terminal identifier and link identifier are different, the terminal identifier is located in the frame body, and the link identifier is located in the Transmitter Address or Receiver Address field of the MAC header.

[0109] It should be noted that, referring to Figure 4 , the device identification element field includes an element identification field (Element ID), a length information field (Length), an element identification extension field (Element ID Extension), a device identification control bitmap field (Device ID Control Bitmap), a device identification status field (Device ID Status), and a device identification information field (Device ID Info.). The element identification field, length information field, element identification information extension field, device identification control bitmap field, and device identification status field are all one byte, and the number of bytes in the device identification information field is variable.

[0110] It should be noted that, referring to Figure 5 , during the transmission of the first and fourth frames, the device identification element field is typically encrypted to improve information transmission security. The encrypted device identification element field yields the device identification key data encapsulation field, which includes the device identification control bitmap field (Device ID Control Bitmap), the device identification status field (Device ID Status), and the device identification information field (Device ID Info.). The device identification control bitmap field and the device identification status field are each one byte, while the number of bytes in the device identification information field is variable.

[0111] It should be noted that, referring to Figures 6 and 7, the structure and purpose of the device identification control bitmap field, device identification identification status field and device identification information field in the device identification element field and the device identification key data encapsulation field are the same. The device identification control bitmap field includes a device identification identification status tag, a device identification tag, multiple link tags, a device identification and link identification sharing indicator tag and a reserved tag, and the device identification information fields include a length field and a device identification field.

[0112] It can be understood that, referring to Figures 9 and 10, the first frame and / or the fourth frame includes a second target field, the terminal identifier includes an identifiable random media access control address IRM, the second target field includes an IRM field, and the terminal identifier and / or at least one link identifier is located in the IRM field.

[0113] It should be noted that the terminal identifier of the multi-link terminal device can be set to an identifiable random media access control address IRM. The IRM is a media access control address randomly assigned to the multi-link terminal device. The multi-link network device can obtain the media access control address of the multi-link terminal device through the IRM, thereby establishing a connection with the multi-link terminal device.

[0114] It should be noted that the link identifier may also be represented by an identifiable random media access control address IRM, and each link identifier is provided with a corresponding identifiable random media access control address IRM.

[0115] It should be noted that the first frame and the fourth frame include a second target field. The structural diagram of the second target field is shown in Figure 9 or Figure 10. The second target field includes an IRM field, and the terminal identifier and / or at least one link identifier are set in the IRM field. The IRM field can contain multiple different IRMs. The number of bytes (octets) of the IRM field is 6N, where 6 is the number of bytes of an IRM and N is the total number of terminal identifiers and link identifiers carried by the first frame and / or the fourth frame, that is, the total number of IRMs. The setting of the number of bytes of the IRM field facilitates the first frame and / or the fourth frame to carry the terminal identifier and / or at least one link identifier.

[0116] It can be understood that, referring to FIG. 9 and FIG. 10 , the second target field further includes an IRM identification status field, and the IRM identification status field is used to indicate whether the IRM of the multi-link terminal device is identified.

[0117] It should be noted that the second target field also includes an IRM identification status field (Device ID Status), and the IRM identification status field is used to indicate whether the IRM of the multi-link terminal device is identified.

[0118] It should be noted that the IRM identification status field is set to 1 byte. When the IRM identification status field is 0, the IRM of the multi-link terminal device is not identified. When the device identification identification status field is 1, the IRM of the multi-link terminal device can be identified.

[0119] It should be noted that the fourth frame received by the multi-link terminal device is a response frame based on the first frame sent by the multi-link network device. When the multi-link network device can identify the IRM of the multi-link terminal device, the IRM identification status field is 1, and when the multi-link network device cannot identify the IRM of the multi-link terminal device, the IRM identification status field is 0.

[0120] It can be understood that, referring to FIG. 9 to FIG. 11 , the second target field further includes an IRM control bitmap field, and the IRM control bitmap field includes one or more of the following fields:

[0121] The IRM identification status tag is used to indicate whether the second target field contains an IRM identification status field.

[0122] IRM tag, used to indicate whether the IRM field contains IRM.

[0123] Multiple link tags are used to indicate whether the IRM field contains the corresponding link identifier.

[0124] The IRM and link identifier share an indicator tag, which is used to indicate whether the IRM and link identifier have the same value.

[0125] It should be noted that the second target field also includes an IRM control bitmap field (IRM control bitmap). The IRM control bitmap field is adapted to the multi-link operation technology. The setting of the IRM control bitmap field provides a basis for the multi-link connection between the multi-link terminal device and the multi-link network device.

[0126] It should be noted that the IRM identification status tag (IRM ID Status) is used to indicate whether the second target field contains the IRM identification status field. The IRM identification status tag occupies 1 bit. When the IRM identification status tag is 0, the second target field does not contain the IRM identification status field. When the IRM identification status tag is 1, the second target field contains the IRM identification status field.

[0127] It should be noted that the multi-link terminal device sends the first frame to the multi-link network device. Although the first frame contains a terminal identifier and / or at least one link identifier, the terminal identifier in the first frame is pre-configured, and the device identifier in the terminal identifier is the device identifier of the multi-link terminal device. Therefore, the second target field of the first frame does not contain the IRM identification field, and the IRM identification status tag is correspondingly set to 0.

[0128] It should be noted that the fourth frame is a response frame to the first frame. After the multi-link network device identifies the multi-link terminal device based on the terminal identifier in the first frame, it generates a fourth frame and sends the fourth frame to the multi-link terminal device. Therefore, the second target field corresponding to the fourth frame contains the IRM identification field, then the IRM identification status tag is 1.

[0129] It should be noted that, referring to Figure 11, the multiple link labels are the first link label (1st.link ID), the second link label (2nd.link ID), and the third link label (3rd.link ID). Each link label corresponds to a corresponding link and can indicate whether the IRM field contains the link identifier of the corresponding link. When the link label is 1, it means that the corresponding link identifier is included in the subsequent IRM field. When the link label is 0, the IRM field does not contain the corresponding link identifier.

[0130] It should be noted that the IRM control bitmap field shown in Figure 11 is configured with three link tags: a first link tag, a second link tag, and a third link tag, each of which occupies one bit. A multi-link terminal device and a multi-link network device each include three links: a first link, a second link, and a third link. The multi-link terminal device and the multi-link network device can connect via any one or more of these three links. The first link, the second link, and the third link are each configured with a corresponding link identifier. For the first frame, when multiple link tags are 1, it indicates that the multi-link terminal device wishes to establish a connection with the multi-link network device over the corresponding links. For example, when the first link tag and the second link tag in the second target field of the first frame are 1, and the third link tag is 0, the IRM field only contains the link identifiers corresponding to the first and second links, indicating that the multi-link terminal device wishes to establish a connection with the multi-link device over the first and second links. For the fourth frame, the values ​​of the multiple link tags in the second target field correspond to those in the first frame. When the identification status field is 1, the IRM of the multi-link terminal device is recognized by the multi-link network device.

[0131] It should be noted that if the multi-link network device is successfully identified and the device identifier of the multi-link terminal device can be recognized by the multi-link network device, then the identification status field of the fourth frame is 1. Based on this, the multi-link terminal device can send a connection request to the multi-link network device so that the multi-link terminal device and the multi-link network device can establish a connection between the corresponding links and realize a multi-link connection.

[0132] It should be noted that the IRM control bitmap field in FIG11 is only an example, and the number of link labels can be set to more or less. The number of link labels in the IRM control bitmap field is determined by the number of links of the multi-link terminal device and the multi-link network device.

[0133] It should be noted that the IRM control bitmap field contains an IRM and link identifier sharing indicator tag, which occupies 1 bit and is used to identify whether the IRM and link identifier have the same value. In multi-link operation technology, one of the link-level MAC addresses of a multi-link terminal device may be the same as the MLD-level MAC address. Therefore, the link identifiers corresponding to multiple links of the same link terminal device are different, but one of the link identifiers may also be the same as the terminal identifier. When the terminal identifier IRM is the same as the IRM corresponding to the link identifier, the IRM and link identifier sharing indicator tag is 1, otherwise it is 0.

[0134] In an exemplary embodiment, the IRM and link identifier sharing indicator is implicit. Specifically, the communication protocol stipulates that the terminal identifier and the link identifier are the same. Therefore, the second target field under the protocol does not need to set the IRM and link identifier sharing indicator separately.

[0135] It should be noted that, referring to FIG. 11 , the IRM control bitmap field also includes a reserved tag (Reserved), which occupies 2 bits.

[0136] It can be understood that, referring to Figure 8, the first frame and the fourth frame include a media access control MAC header and a frame body respectively, the second target field is located in the MAC header or the frame body, and the second target field is an IRM element field or an IRM key data encapsulation field.

[0137] It should be noted that the first frame and the fourth frame include a media access control MAC header and a frame body respectively, and the second target field is located in the frame body or the MAC header. The second target field is an IRM element field or an IRM key data encapsulation field.

[0138] It should be noted that when the terminal identifier and link identifier in the second destination field are the same, the terminal identifier is located in the Transmitter Address (TA) or Receiver Address (RA) field of the MAC header. When the terminal identifier and link identifier are different, the terminal identifier is located in the frame body, and the link identifier is located in the Transmitter Address or Receiver Address field of the MAC header.

[0139] It should be noted that, referring to Figure 9, the IRM element field includes an element identification field (Element ID), a length information field (Length), an element identification extension field (Element ID Extension), an IRM control bitmap field (IRM control bitmap), an IRM identification status field (IRM Status), and an IRM field (IRM info.). The element identification field, length information field, element identification information extension field, IRM control bitmap field, and IRM identification status field are all one byte, and the number of bytes in the IRM field is set to 6N, where N is the number of IRMs.

[0140] It should be noted that, referring to Figure 10, during the transmission of the first and fourth frames, in order to improve the security of information transmission, the IRM element field is usually encrypted for transmission. After the IRM element field is encrypted, an IRM key data encapsulation field is obtained, which includes an IRM control bitmap field (IRM control bitmap), an IRM identification status field (IRM Status), and an IRM field (IRM info.). Among them, the IRM control bitmap field and the IRM identification status field are both one byte, and the number of bytes of the IRM field is set to be variable.

[0141] It should be noted that, referring to Figure 11, the structure and purpose of the IRM control bitmap field, IRM identification status field and IRM information field in the IRM element field and the IRM key data encapsulation field are the same. The IRM control bitmap field includes an IRM identification status tag, an IRM tag, multiple link tags, an IRM and link identification sharing indicator tag and a retention tag.

[0142] It can be understood that, referring to FIG12 , the terminal identifier and / or at least one link identifier is generated by the multi-link terminal device; before step S120 , the communication method provided in the embodiment of the present application further includes but is not limited to the following steps:

[0143] Step S140: The multi-link terminal device sends a terminal identifier and / or at least one link identifier to the multi-link network device via a second frame.

[0144] It should be noted that before the multi-link terminal device sends the first frame to the multi-link network device, the multi-link terminal device sends the terminal identifier and / or at least one link identifier to the multi-link network device through the second frame. The multi-link network device saves the terminal identifier and / or at least one link identifier carried by the second frame locally or in other multi-link network devices associated with the local area, so that the multi-link network device can later identify the terminal identifier and link identifier.

[0145] It can be understood that the second frame includes at least one of the following: the second authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; the fourth authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; the (re)association request frame in the fast initial connection establishment FILS process between the multi-link terminal device and the multi-link network device; the first authentication frame in the PASN three-way handshake process for security negotiation before connection between the multi-link terminal device and the multi-link network device; the third authentication frame in the PSAN three-way handshake process between the multi-link terminal device and the multi-link network device.

[0146] It should be noted that the four-way handshake protocol is used to negotiate unicast keys. Its main purpose is to ensure that the keys obtained by the applicant and the authenticator are the same and up-to-date. The required pairwise transient key (PTK) can be generated through the four-way handshake. The specific process is as follows: The multi-link network device sends the first authentication frame in the four-way handshake to the multi-link terminal device. The multi-link terminal device sends the second authentication frame in the four-way handshake to the multi-link network device. Upon receiving the second authentication frame in the four-way handshake, the multi-link network device generates the PTK on the multi-link network device side and replies with the third authentication frame in the four-way handshake to the multi-link terminal device. Upon receiving the third authentication frame in the four-way handshake, the multi-link terminal device generates the PTK on the multi-link terminal device side and replies with the fourth authentication frame in the four-way handshake to the multi-link network device. Therefore, the second frame includes the second and fourth authentication frames in the four-way handshake between the multi-link terminal device and the multi-link network device.

[0147] It should be noted that the (re)association request frame between a multi-link terminal device and a multi-link network device during the fast initial connection establishment (FILS) process is also the second frame. Fast initial connection is mainly used to accelerate the connection between a multi-link terminal device and a multi-link network device. Fast initial connection establishment (FILS) is defined in 802.11ai, enabling wireless access points (APs), i.e., multi-link network devices, to periodically send discovery frames with a period of 20 milliseconds. Compared with beacons, this period is shorter, allowing multi-link terminal devices to discover multi-link network devices more quickly. In addition, the FILS (re)association contains Dynamic Host Configuration Protocol (DHCP) information, which can configure the address at the same time as the association.

[0148] It should be noted that this is the third authentication frame in the PSAN three-way handshake process between the link terminal device and the multi-link network device.

[0149] It should be noted that, referring to Figure 13, during the first connection process, the first terminal device in the multi-link terminal device discovers the multi-link network device that supports the multi-link operation technology by receiving a beacon and / or a probe response frame; the multi-link terminal device and the multi-link network device complete the multi-link authentication and connection through the multi-link authentication and connection process; during the four-way handshake process, the frame sent by the first terminal device of the multi-link terminal device to the first network device contains a terminal identifier and / or at least one link identifier, and the frame is the second frame. After receiving the terminal identifier and / or at least one link identifier, the first network device of the multi-link network device saves it locally or in other multi-link network devices associated with the local area; after the multi-link terminal device completes the communication with the multi-link network device, it disconnects through the disassociation and de-authentication process. During the second connection process, on the second link, i.e., the link connecting the second network device and the second terminal device, the multi-link terminal device sends an identifiable management frame that may carry the second link identifier to the multi-link network device; on the second link, after receiving the management frame, the multi-link network device generates a corresponding management frame response; on the first link, i.e., the link connecting the first network device and the first terminal device, the multi-link terminal device sends an identifiable management frame that may carry the first link identifier to the multi-link network device; on the first link, after receiving the management frame, the multi-link network device generates a corresponding management frame response. response); on the first or second link, the multi-link terminal device sends an authentication (Authentication) and (re)association ((re)Association) frame carrying the terminal identifier to the multi-link network device; after receiving the authentication and (re)association frame carrying the terminal identifier, the multi-link network device retrieves the corresponding terminal identifier information on the corresponding link and responds; during the four-way handshake process, the multi-link network device indicates whether the multi-link terminal device can be identified by the terminal identifier, and the frame sent by the multi-link terminal device to the multi-link network device includes but is not limited to the new terminal identifier and / or at least one new link identifier.

[0150] It can be understood that, referring to FIG14 , the terminal identifier and / or at least one link identifier is generated by the multi-link network device; before step S110, the communication method provided in the embodiment of the present application further includes but is not limited to the following steps:

[0151] Step S150: The multi-link terminal device receives the third frame sent by the multi-link network device.

[0152] Step S160: The multi-link terminal device obtains a terminal identifier and / or at least one link identifier from the third frame.

[0153] It should be noted that before the multi-link terminal device obtains the pre-configured terminal identifier and / or at least one link identifier, the multi-link terminal device receives the third frame sent by the multi-link network device and obtains the terminal identifier and / or at least one link identifier from the third frame. The terminal identifier and / or at least one link identifier are generated by the multi-link network device. The sending of the third frame enables the multi-link network device and the multi-link terminal device to have the same terminal identifier and link identifier, which facilitates the multi-link network device to identify the terminal identifier and link identifier later.

[0154] It can be understood that the third frame includes at least one of the following: the third authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; the (re)association response frame in the FILS process between the multi-link terminal device and the multi-link network device; the second authentication frame in the PASN three-way handshake process between the multi-link terminal device and the multi-link network device.

[0155] It should be noted that the four-way handshake protocol is used to negotiate unicast keys. Its main purpose is to ensure that the keys obtained by the applicant and the authenticator are the same and up-to-date. The required pairwise transient key (PTK) can be generated through the four-way handshake. The specific process is as follows: The multi-link network device sends the first authentication frame in the four-way handshake to the multi-link terminal device. The multi-link terminal device sends the second authentication frame in the four-way handshake to the multi-link network device. Upon receiving the second authentication frame in the four-way handshake, the multi-link network device generates the PTK on the multi-link network device side and responds with the third authentication frame in the four-way handshake to the multi-link terminal device. Upon receiving the third authentication frame in the four-way handshake, the multi-link terminal device generates the PTK on the multi-link terminal device side and responds with the fourth authentication frame in the four-way handshake to the multi-link network device. Therefore, the third frame includes the third authentication frame in the four-way handshake between the multi-link terminal device and the multi-link network device.

[0156] It should be noted that the (re)association response frame corresponds to the (re)association request frame.

[0157] It should be noted that, referring to Figure 15, during the first connection process, the first terminal device in the multi-link terminal device discovers the multi-link network device that supports the multi-link operation technology by receiving a beacon and / or a probe response frame; the multi-link terminal device and the multi-link network device complete the multi-link authentication and connection through the multi-link authentication and connection process; during the four-way handshake process, the frame sent by the first network device of the multi-link network device to the first terminal device contains a terminal identifier and / or at least one link identifier, and the frame is the second frame. After receiving the terminal identifier and / or at least one link identifier, the first terminal device of the multi-link terminal device saves it locally or in other multi-link network devices associated with the local area; after the multi-link terminal device completes the communication with the multi-link network device, it disconnects through the disassociation and de-authentication process. During the second connection process, on the second link, i.e., the link connecting the second network device and the second terminal device, the multi-link terminal device sends an identifiable management frame that may carry the second link identifier to the multi-link network device; on the second link, after receiving the management frame, the multi-link network device generates a corresponding management frame response; on the first link, i.e., the link connecting the first network device and the first terminal device, the multi-link terminal device sends an identifiable management frame that may carry the first link identifier to the multi-link network device; on the first link, after receiving the management frame, the multi-link network device generates a corresponding management frame response. response); on the first or second link, the multi-link terminal device sends an authentication (Authentication) and (re)association ((re)Association) frame carrying the terminal identifier to the multi-link network device; after receiving the authentication and (re)association frame carrying the terminal identifier, the multi-link network device retrieves the corresponding terminal identifier information on the corresponding link and responds; during the four-way handshake process, the multi-link network device indicates whether the multi-link terminal device can be identified by the terminal identifier, and the frame sent by the multi-link network device to the multi-link terminal device includes but is not limited to the new terminal identifier and / or at least one new link identifier.

[0158] It can be understood that the first frame is an access network query protocol ANQP request frame, and the fourth frame includes one or more pieces of recommended connection multi-link network device information and link information corresponding to each piece of recommended connection multi-link network device information.

[0159] It should be noted that the multi-link terminal device sends an ANQP request frame (ANQP neighbor query) to the multi-link network device. The multi-link network device can implement access control (Access Control) based on the terminal identifier or link identifier provided by the multi-link network device. Specifically, the multi-link terminal device sends an ANQP request frame including a terminal identifier and / or at least one link identifier to the multi-link network device. The multi-link network device identifies the terminal identifier and / or at least one link identifier in the ANQP request frame, thereby implementing a multi-link connection with the multi-link terminal device.

[0160] It can be understood that the first frame is a connection request frame; the fourth frame contains one or more of the following information: link indication information allowing link establishment, the number of links allowed to establish link connections, whether the link requested for connection is allowed to establish a connection, and whether the terminal device requested for connection is allowed to establish a connection.

[0161] It should be noted that the multi-link network device identifies the terminal identifier and / or at least one link identifier of the first frame, i.e., the connection request frame, determines whether it is the same as the existing terminal identifier and link identifier, and generates a fourth frame. The fourth frame includes one or more of the following information: link indication information allowing link establishment, the number of links allowed to establish link connections, whether the link requested to be connected is allowed to establish a connection, and whether the terminal device requesting to be connected is allowed to establish a connection.

[0162] In addition, referring to FIG16 , FIG16 is a flow chart of a communication method provided in an embodiment of the present application at a multi-link network device. The communication method provided in an embodiment of the present application includes but is not limited to the following steps:

[0163] Step S210: The multi-link network device receives a first frame sent by a multi-link terminal device, where the first frame includes a terminal identifier and / or at least one link identifier.

[0164] Step S220: The multi-link network device identifies the multi-link terminal device and the link according to the terminal identifier and / or at least one link identifier.

[0165] It should be noted that the first frame sent by the multi-link terminal device and received by the multi-link network device carries a terminal identifier and / or at least one link identifier. The terminal identifier corresponds to the multi-link terminal device, and the link identifier corresponds one-to-one to the link. The multi-link network device identifies the multi-link terminal device and / or the link based on the terminal identifier and / or at least one link identifier, thereby establishing a multi-link connection, and provides corresponding network access services to the multi-link terminal device based on the multi-link connection, and manages the multi-link terminal device. In addition, the setting of the terminal identifier and the link identifier can reduce the sniffing positioning of third-party devices and improve the security of communication.

[0166] In one embodiment, the multi-link network device identifies the multi-link terminal device and / or the link using a terminal identifier and / or at least one link identifier, and feeds back identification result information to the multi-link terminal device. If the multi-link terminal device and / or the link of the multi-link terminal device is successfully identified by the multi-link network device, the multi-link network device feeds back the information to the multi-link terminal device. As a result, the multi-link terminal device can send a connection request to the multi-link network device, so that the multi-link network device and the multi-link terminal device establish a multi-link connection, i.e., transmit data simultaneously over multiple links. The establishment of the multi-link connection can provide corresponding network access services for the multi-link terminal device.

[0167] It should be noted that multi-link connections allow multi-link network devices and multi-link terminal devices to transmit data simultaneously on multiple links, thereby improving data transmission throughput, reducing data transmission latency, and thus improving communication efficiency.

[0168] It should be noted that the terminal identifier corresponds to the multi-link terminal device, and the multi-link network device can identify the multi-link terminal device based on the terminal identifier, and the link identifier corresponds one-to-one to the link that the multi-link terminal device can connect to. The multi-link network device can identify the corresponding link based on the link identifier, thereby establishing a connection with the multi-link terminal device.

[0169] It should be noted that in multi-link operation technology, MAC addresses are divided into link-level MAC addresses and MLD-level MAC addresses. A multi-link terminal device typically includes a unique MLD-level MAC address and at least one link-level MAC address. The MLD-level MAC address uniquely identifies a multi-link terminal device. Therefore, a multi-link terminal device corresponds to a link identifier, and a multi-link network device can identify the unique corresponding multi-link terminal device through the link identifier. In addition, each link-level MAC address of the same multi-link terminal device is different, but one of the link-level MAC addresses of the multi-link terminal device may be the same as the MLD-level MAC address. Therefore, the link identifiers corresponding to multiple links of the same link terminal device are different, and one of the link identifiers may also be the same as the terminal identifier. When the frame used for multi-link terminal device identification carries only the link-level MAC address, the first frame only needs to carry the link identifier. When the link identifier is the same as the terminal identifier, the first frame only needs to carry the terminal identifier or the link identifier. When the frame used for multi-link terminal device identification carries both the current link-level MAC address and the MLD-level MAC address, the first frame carries the terminal identifier and a link identifier. When a frame used for multi-link terminal device identification carries the MAC address of the current link level, MAC addresses of other link levels, and a MAC address of the MLD level at the same time, the first frame carries the terminal identifier and multiple link identifiers.

[0170] It should be noted that the terminal identifier and the link identifier can be configured through a multi-link terminal device or a multi-link network device.

[0171] It should be noted that the first frame is encrypted and transmitted between the multi-link terminal device and the multi-link network device. Therefore, the terminal identifier and link identifier carried by the first frame cannot be sniffed and tracked by third-party devices, thereby improving the security of communication transmission.

[0172] It should be noted that the first frame is a frame sent by the multi-link terminal device to the multi-link network device. The frame is usually used to request a connection with the multi-link network device, such as an association request frame in the FILS mode.

[0173] It should be noted that the encrypted transmission of the first frame can be achieved through a key. Specifically, the multi-link terminal device and the multi-link network device generate a multi-link operation-level pairwise transmission key (Pairwise Transient, KeyPTK) and a link-level group temporary key (Group Temporal Key, GTK) on a link through a four-way handshake. These are used to encrypt and decrypt the transmitted unicast data frames and anchor data frames, respectively, to ensure the security of data transmission.

[0174] It is understood that, referring to FIG. 17 , step S220 further includes but is not limited to the following steps:

[0175] Step S230: The multi-link network device sends a fourth frame to the multi-link terminal device, where the fourth frame is a response frame to the first frame.

[0176] It should be noted that after receiving the first frame, the multi-link network device identifies the terminal identifier and link identifier, that is, determines whether the same terminal identifier and link identifier are stored locally or in another multi-link network device associated with the multi-link network. Based on the determination result, the device generates a fourth frame and sends the fourth frame to the multi-link terminal device. Thus, the fourth frame is a response frame to the first frame. If the fourth frame indicates that the same terminal identifier and link identifier are stored locally or in a network associated with the multi-link network device, the multi-link terminal device establishes a multi-link connection with the multi-link network device and performs data transmission. Otherwise, the connection between the multi-link terminal device and the multi-link network device cannot be successfully established.

[0177] It can be understood that, referring to Figures 4 and 5, the first frame and / or the fourth frame contains a first target field, the terminal identifier contains a device identifier, the first target field includes a device identification information field, and the terminal identifier and / or at least one link identifier is located in the device identification information field.

[0178] It should be noted that the terminal identifier of the multi-link terminal device can be set to a device ID, which is the device ID of the multi-link terminal device. The multi-link network device can obtain the ID of the multi-link terminal device by identifying the device ID.

[0179] It should be noted that the link identifier may also be represented by a device identifier, and each link identifier is provided with a corresponding device identifier.

[0180] It should be noted that the first and fourth frames include a first destination field. The structure of the first destination field is shown in FIG4 or FIG5 . The first destination field includes a device identification information field (device ID info.), and a terminal identifier and / or at least one link identifier are set in the device identification information field. The device identification information field can include multiple different device identifiers. The number of octets in the device identification information field is variable, and its specific value can be set according to the number of terminal identifiers and link identifiers.

[0181] It can be understood that, referring to FIG. 4 and FIG. 5 , the first target field further includes a device identification recognition status field, and the device identification recognition status field is used to indicate whether the device identification of the multi-link terminal device is recognized.

[0182] It should be noted that the first target field also includes a device identification status field (Device ID Status), and the device identification status field is used to indicate whether the device identification of the multi-link terminal device is identified.

[0183] It should be noted that the device identification status field is set to 1 byte. When the device identification status field is 0, the device identification of the multi-link terminal device is not identified. When the device identification status field is 1, the device identification of the multi-link terminal device can be identified.

[0184] It should be noted that the fourth frame received by the multi-link terminal device is a response frame based on the first frame sent by the multi-link network device. When the multi-link network device can identify the terminal identifier of the multi-link terminal device, the device identifier identification status field is 1, and the multi-link network device and the multi-link terminal device can establish a connection. When the multi-link network device cannot identify the terminal identifier of the multi-link terminal device, the device identifier identification status field is 0, and the connection between the multi-link network device and the multi-link terminal device fails to be established.

[0185] It can be understood that, referring to FIG. 4 to FIG. 6 , the first target field further includes a device identification control bitmap field, and the device identification control bitmap field includes one or more of the following fields:

[0186] The device identification recognition status tag is used to indicate whether the first target field includes a device identification recognition status field.

[0187] The device identification tag is used to indicate whether the device identification information field contains the device identification.

[0188] Multiple link tags are used to indicate whether the device identification information field contains a corresponding link identifier.

[0189] The device identifier and link identifier share an indicator tag, which is used to indicate whether the device identifier and the link identifier have the same value.

[0190] It should be noted that the first target field also includes a device identification control bitmap field (Device ID control bitmap), which is compatible with the multi-link operation technology. The setting of the device identification control bitmap field provides a basis for the multi-link connection between the multi-link terminal device and the multi-link network device.

[0191] It should be noted that the device identification status tag (Device ID Status) is used to indicate whether the first target field contains the device identification status field. The device identification status tag occupies 1 bit. When the device identification status tag is 0, the first target field does not contain the device identification status field. When the device identification status tag is 1, the first target field contains the device identification status field.

[0192] It should be noted that the multi-link terminal device sends the first frame to the multi-link network device. Although the first frame contains a terminal identifier and / or at least one link identifier, the terminal identifier in the first frame is pre-configured, and the device identifier in the terminal identifier is the device identifier of the multi-link terminal device. Therefore, the first target field of the first frame does not include a device identifier identification field, and the device identifier identification status tag is correspondingly set to 0.

[0193] It should be noted that the fourth frame is a response frame to the first frame. After the multi-link network device identifies the multi-link terminal device based on the terminal identifier in the first frame, it generates a fourth frame and sends the fourth frame to the multi-link terminal device. Therefore, the first target field corresponding to the fourth frame contains the device identification recognition field, then the device identification recognition status tag is 1.

[0194] It should be noted that, referring to Figure 6, the multiple link labels are the first link label (1st.link ID), the second link label (2nd.link ID), and the third link label (3rd.link ID). Each link label corresponds to a corresponding link and can indicate whether the device identification information field contains the link identifier of the corresponding link. When the link label is 1, it indicates that the corresponding link identifier is included in the subsequent device identification information field. When the link label is 0, the device identification information field does not contain the corresponding link identifier.

[0195] It should be noted that the device identification control bitmap field shown in Figure 6 is configured with three link tags: a first link tag, a second link tag, and a third link tag, each of which occupies one bit. A multi-link terminal device and a multi-link network device both include three links: a first link, a second link, and a third link. The multi-link terminal device and the multi-link network device can connect via any one or more of these three links. The first link, the second link, and the third link are each configured with a corresponding link identifier. For the first frame, when multiple link tags are 1, it indicates that the multi-link terminal device wishes to establish a connection with the multi-link network device over the corresponding links. For example, when the first link tag and the second link tag in the first target field of the first frame are 1, and the third link tag is 0, the device identification information field only contains the link identifiers corresponding to the first and second links, indicating that the multi-link terminal device wishes to establish a connection with the multi-link device over the first and second links. For the fourth frame, the values ​​of the multiple link tags in the first target field correspond to those in the first frame. When the identification status field is 1, the device identifier of the multi-link terminal device can be recognized by the multi-link network device.

[0196] It should be noted that if the multi-link network device is successfully identified and the device identifier of the multi-link terminal device can be recognized by the multi-link network device, then the identification status field of the fourth frame is 1. Based on this, the multi-link terminal device can send a connection request to the multi-link network device so that the multi-link terminal device and the multi-link network device can establish a connection between the corresponding links and realize a multi-link connection.

[0197] It should be noted that the device identification control bitmap field in FIG6 is only an example. The number of link labels can be set to more or less. The number of link labels in the device identification control bitmap field is determined by the number of links of the multi-link terminal device and the multi-link network device.

[0198] It should be noted that the device identification control bitmap field contains a device identification and link identification sharing indicator tag, which occupies one bit and is used to identify whether the device identification and link identification have the same value. In multi-link operation technology, one of the link-level MAC addresses of a multi-link terminal device may be the same as the MLD-level MAC address. Therefore, the link identifiers corresponding to multiple links of the same link terminal device are different, but one of the link identifiers may also be the same as the terminal identifier. When the device identification and link identifier are the same, the device identification and link identification sharing indicator tag is 1, otherwise it is 0.

[0199] In an exemplary embodiment, the device identifier and link identifier sharing indicator are implicit. Specifically, the communication protocol stipulates that the terminal identifier and the link identifier are the same. Therefore, the first target field under the protocol does not need to set the device identifier and link identifier sharing indicator separately.

[0200] It should be noted that, referring to FIG. 6 , the device identification control bitmap field also includes a reserved tag (Reserved), which occupies 2 bits.

[0201] It can be understood that, referring to FIG. 7 , the device identification information field includes a length field and a device identification field.

[0202] It should be noted that the device identification information field includes a length field (length) and a device identification field (Device ID). The device identification field is used to store the device identification of the multi-link terminal device, and the length field is used to indicate the length of the device identification of the multi-link terminal device.

[0203] It can be understood that, referring to Figure 8, the first frame and the fourth frame include a media access control MAC header and a frame body respectively, the first target field is located in the MAC header or the frame body, and the first target field is a device identification element field or a device identification key data encapsulation field.

[0204] It should be noted that the first frame and the fourth frame include a media access control MAC header and a frame body, respectively, and the first target field is located in the frame body or the MAC header. The first target field is a device identification element field or a device identification key data encapsulation field.

[0205] It should be noted that when the terminal identifier and link identifier are the same, the terminal identifier is located in the Transmitter Address (TA) or Receiver Address (RA) field of the MAC header. When the terminal identifier and link identifier are different, the terminal identifier is located in the frame body, and the link identifier is located in the Transmitter Address or Receiver Address field of the MAC header.

[0206] It should be noted that, referring to Figure 4 , the device identification element field includes an element identification field (Element ID), a length information field (Length), an element identification extension field (Element ID Extension), a device identification control bitmap field (Device ID Control Bitmap), a device identification status field (Device ID Status), and a device identification information field (Device ID Info.). The element identification field, length information field, element identification information extension field, device identification control bitmap field, and device identification status field are all one byte, and the number of bytes in the device identification information field is variable.

[0207] It should be noted that, referring to Figure 5 , during the transmission of the first and fourth frames, the device identification element field is typically encrypted to improve information transmission security. The encrypted device identification element field yields the device identification key data encapsulation field, which includes the device identification control bitmap field (Device ID Control Bitmap), the device identification status field (Device ID Status), and the device identification information field (Device ID Info.). The device identification control bitmap field and the device identification status field are each one byte, while the number of bytes in the device identification information field is variable.

[0208] It should be noted that, referring to Figures 6 and 7, the structure and purpose of the device identification control bitmap field, device identification identification status field and device identification information field in the device identification element field and the device identification key data encapsulation field are the same. The device identification control bitmap field includes a device identification identification status tag, a device identification tag, multiple link tags, a device identification and link identification sharing indicator tag and a reserved tag, and the device identification information fields include a length field and a device identification field.

[0209] It can be understood that, referring to Figures 9 and 10, the first frame and / or the fourth frame includes a second target field, the terminal identifier includes an identifiable random media access control address IRM, the second target field includes an IRM field, and the terminal identifier and / or at least one link identifier is located in the IRM field.

[0210] It should be noted that the terminal identifier of the multi-link terminal device can be set to an identifiable random media access control address IRM. The IRM is a media access control address randomly assigned to the multi-link terminal device. The multi-link network device can obtain the media access control address of the multi-link terminal device through the IRM, thereby establishing a connection with the multi-link terminal device.

[0211] It should be noted that the link identifier may also be represented by an identifiable random media access control address IRM, and each link identifier is provided with a corresponding identifiable random media access control address IRM.

[0212] It should be noted that the first frame and the fourth frame include a second target field. The structural diagram of the second target field is shown in Figure 9 or Figure 10. The second target field includes an IRM field, and the terminal identifier and / or at least one link identifier are set in the IRM field. The IRM field can contain multiple different IRMs. The number of bytes (octets) of the IRM field is 6N, where 6 is the number of bytes of an IRM and N is the total number of terminal identifiers and link identifiers carried by the first frame and / or the fourth frame, that is, the total number of IRMs. The setting of the number of bytes of the IRM field facilitates the first frame and / or the fourth frame to carry the terminal identifier and / or at least one link identifier.

[0213] It can be understood that, referring to FIG. 9 and FIG. 10 , the second target field further includes an IRM identification status field, and the IRM identification status field is used to indicate whether the IRM of the multi-link terminal device is identified.

[0214] It should be noted that the second target field also includes an IRM identification status field (Device ID Status), and the IRM identification status field is used to indicate whether the IRM of the multi-link terminal device is identified.

[0215] It should be noted that the IRM identification status field is set to 1 byte. When the IRM identification status field is 0, the IRM of the multi-link terminal device is not identified. When the device identification identification status field is 1, the IRM of the multi-link terminal device can be identified.

[0216] It should be noted that the fourth frame received by the multi-link terminal device is a response frame based on the first frame sent by the multi-link network device. When the multi-link network device can identify the IRM of the multi-link terminal device, the IRM identification status field is 1, and when the multi-link network device cannot identify the IRM of the multi-link terminal device, the IRM identification status field is 0.

[0217] It can be understood that, referring to FIG. 9 to FIG. 11 , the second target field further includes an IRM control bitmap field, and the IRM control bitmap field includes one or more of the following fields:

[0218] The IRM identification status tag is used to indicate whether the second target field contains an IRM identification status field.

[0219] IRM tag, used to indicate whether the IRM field contains IRM.

[0220] Multiple link tags are used to indicate whether the IRM field contains the corresponding link identifier.

[0221] The IRM and link identifier share an indicator tag, which is used to indicate whether the IRM and link identifier have the same value.

[0222] It should be noted that the second target field also includes an IRM control bitmap field (IRM control bitmap). The IRM control bitmap field is adapted to the multi-link operation technology. The setting of the IRM control bitmap field provides a basis for the multi-link connection between the multi-link terminal device and the multi-link network device.

[0223] It should be noted that the IRM identification status tag (IRM ID Status) is used to indicate whether the second target field contains the IRM identification status field. The IRM identification status tag occupies 1 bit. When the IRM identification status tag is 0, the second target field does not contain the IRM identification status field. When the IRM identification status tag is 1, the second target field contains the IRM identification status field.

[0224] It should be noted that the multi-link terminal device sends the first frame to the multi-link network device. Although the first frame contains a terminal identifier and / or at least one link identifier, the terminal identifier in the first frame is pre-configured, and the device identifier in the terminal identifier is the device identifier of the multi-link terminal device. Therefore, the second target field of the first frame does not contain the IRM identification field, and the IRM identification status tag is correspondingly set to 0.

[0225] It should be noted that the fourth frame is a response frame to the first frame. After the multi-link network device identifies the multi-link terminal device based on the terminal identifier in the first frame, it generates a fourth frame and sends the fourth frame to the multi-link terminal device. Therefore, the second target field corresponding to the fourth frame contains the IRM identification field, then the IRM identification status tag is 1.

[0226] It should be noted that, referring to Figure 11, the multiple link labels are the first link label (1st.link ID), the second link label (2nd.link ID), and the third link label (3rd.link ID). Each link label corresponds to a corresponding link and can indicate whether the IRM field contains the link identifier of the corresponding link. When the link label is 1, it means that the corresponding link identifier is included in the subsequent IRM field. When the link label is 0, the IRM field does not contain the corresponding link identifier.

[0227] It should be noted that the IRM control bitmap field shown in Figure 11 is configured with three link tags: a first link tag, a second link tag, and a third link tag, each of which occupies one bit. A multi-link terminal device and a multi-link network device each include three links: a first link, a second link, and a third link. The multi-link terminal device and the multi-link network device can connect via any one or more of these three links. The first link, the second link, and the third link are each configured with a corresponding link identifier. For the first frame, when multiple link tags are 1, it indicates that the multi-link terminal device wishes to establish a connection with the multi-link network device over the corresponding links. For example, when the first link tag and the second link tag in the second target field of the first frame are 1, and the third link tag is 0, the IRM field only contains the link identifiers corresponding to the first and second links, indicating that the multi-link terminal device wishes to establish a connection with the multi-link device over the first and second links. For the fourth frame, the values ​​of the multiple link tags in the second target field correspond to those in the first frame. When the identification status field is 1, the IRM of the multi-link terminal device is recognized by the multi-link network device.

[0228] It should be noted that if the multi-link network device is successfully identified and the device identifier of the multi-link terminal device can be recognized by the multi-link network device, then the identification status field of the fourth frame is 1. Based on this, the multi-link terminal device can send a connection request to the multi-link network device so that the multi-link terminal device and the multi-link network device can establish a connection between the corresponding links and realize a multi-link connection.

[0229] It should be noted that the IRM control bitmap field in FIG11 is only an example, and the number of link labels can be set to more or less. The number of link labels in the IRM control bitmap field is determined by the number of links of the multi-link terminal device and the multi-link network device.

[0230] It should be noted that the IRM control bitmap field contains an IRM and link identifier sharing indicator tag, which occupies 1 bit and is used to identify whether the IRM and link identifier have the same value. In multi-link operation technology, one of the link-level MAC addresses of a multi-link terminal device may be the same as the MLD-level MAC address. Therefore, the link identifiers corresponding to multiple links of the same link terminal device are different, but one of the link identifiers may also be the same as the terminal identifier. When the terminal identifier IRM is the same as the IRM corresponding to the link identifier, the IRM and link identifier sharing indicator tag is 1, otherwise it is 0.

[0231] In one embodiment, the IRM and link identifier sharing indicator is implicit. Specifically, the communication protocol stipulates that the terminal identifier and the link identifier are the same. Therefore, the second target field under the protocol does not need to set the IRM and link identifier sharing indicator separately.

[0232] It should be noted that, referring to FIG. 11 , the IRM control bitmap field also includes a reserved tag (Reserved), which occupies 2 bits.

[0233] It can be understood that, referring to Figure 8, the first frame and the fourth frame include a media access control MAC header and a frame body respectively, the second target field is located in the MAC header or the frame body, and the second target field is an IRM element field or an IRM key data encapsulation field.

[0234] It should be noted that the first frame and the fourth frame include a media access control MAC header and a frame body respectively, and the second target field is located in the frame body. The second target field is an IRM element field or an IRM key data encapsulation field.

[0235] It should be noted that when the terminal identifier and link identifier in the second destination field are the same, the terminal identifier is located in the Transmitter Address (TA) or Receiver Address (RA) field of the MAC header. When the terminal identifier and link identifier are different, the terminal identifier is located in the frame body, and the link identifier is located in the Transmitter Address or Receiver Address field of the MAC header.

[0236] It should be noted that, referring to Figure 9, the IRM element field includes an element identification field (Element ID), a length information field (Length), an element identification extension field (Element ID Extension), an IRM control bitmap field (IRM control bitmap), an IRM identification status field (IRM Status), and an IRM information field (IRM info.). The element identification field, the length information field, the element identification information extension field, the IRM control bitmap field, and the IRM identification status field are all one byte, and the number of bytes of the IRM field is set to 6N, where N is the number of IRMs.

[0237] It should be noted that, referring to Figure 10, during the transmission of the first and fourth frames, in order to improve the security of information transmission, the IRM element field is usually encrypted for transmission. After the IRM element field is encrypted, an IRM key data encapsulation field is obtained, which includes an IRM control bitmap field (IRM control bitmap), an IRM identification status field (IRM Status), and an IRM field (IRM info.). Among them, the IRM control bitmap field and the IRM identification status field are both one byte, and the number of bytes of the IRM field is set to be variable.

[0238] It should be noted that, referring to Figure 11, the structure and purpose of the IRM control bitmap field, IRM identification status field and IRM information field in the IRM element field and the IRM key data encapsulation field are the same. The IRM control bitmap field includes an IRM identification status tag, an IRM tag, multiple link tags, an IRM and link identification sharing indicator tag and a retention tag.

[0239] 18 , the terminal identifier and / or at least one link identifier is generated by the multi-link terminal device; before step S210 , the communication method provided in the embodiment of the present application further includes but is not limited to the following steps:

[0240] Step S240: The multi-link network device receives the second frame sent by the multi-link terminal device.

[0241] Step S250: The multi-link network device obtains a terminal identifier and / or at least one link identifier from the second frame.

[0242] It should be noted that before the multi-link network device receives the first frame sent by the multi-link terminal device, the multi-link network device receives the second frame sent by the multi-link terminal device and obtains the terminal identifier and / or at least one link identifier from the second frame. The multi-link network device saves the terminal identifier and / or at least one link identifier carried by the second frame locally or in other multi-link network devices associated with the local area, so that the multi-link network device can later identify the terminal identifier and link identifier.

[0243] It can be understood that the second frame includes at least one of the following: the second authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; the fourth authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; the (re)association request frame in the fast initial connection establishment FILS process between the multi-link terminal device and the multi-link network device; the first authentication frame in the PASN three-way handshake process for security negotiation before connection between the multi-link terminal device and the multi-link network device; the third authentication frame in the PSAN three-way handshake process between the multi-link terminal device and the multi-link network device.

[0244] It should be noted that the four-way handshake protocol is used to negotiate unicast keys. Its main purpose is to ensure that the keys obtained by the applicant and the authenticator are the same and up-to-date. The required pairwise transient key (PTK) can be generated through the four-way handshake. The specific process is as follows: The multi-link network device sends the first authentication frame in the four-way handshake to the multi-link terminal device. The multi-link terminal device sends the second authentication frame in the four-way handshake to the multi-link network device. Upon receiving the second authentication frame in the four-way handshake, the multi-link network device generates the PTK on the multi-link network device side and replies with the third authentication frame in the four-way handshake to the multi-link terminal device. Upon receiving the third authentication frame in the four-way handshake, the multi-link terminal device generates the PTK on the multi-link terminal device side and replies with the fourth authentication frame in the four-way handshake to the multi-link network device. Therefore, the second frame includes the second and fourth authentication frames in the four-way handshake between the multi-link terminal device and the multi-link network device.

[0245] It should be noted that the (re)association request frame between a multi-link terminal device and a multi-link network device during the fast initial connection establishment (FILS) process is also the second frame. Fast initial connection is mainly used to accelerate the connection between a multi-link terminal device and a multi-link network device. Fast initial connection establishment (FILS) is defined in 802.11ai, enabling wireless access points (APs), i.e., multi-link network devices, to periodically send discovery frames with a period of 20 milliseconds. Compared with beacons, this period is shorter, allowing multi-link terminal devices to discover multi-link network devices more quickly. In addition, the FILS (re)association contains Dynamic Host Configuration Protocol (DHCP) information, which can configure the address at the same time as the association.

[0246] It should be noted that this is the third authentication frame in the PSAN three-way handshake process between the link terminal device and the multi-link network device.

[0247] It should be noted that, referring to Figure 13, during the first connection process, the first terminal device in the multi-link terminal device discovers the multi-link network device that supports the multi-link operation technology by receiving a beacon and / or a probe response frame; the multi-link terminal device and the multi-link network device complete the multi-link authentication and connection through the multi-link authentication and connection process; during the four-way handshake process, the frame sent by the first terminal device of the multi-link terminal device to the first network device contains a terminal identifier and / or at least one link identifier, and the frame is the second frame. After receiving the terminal identifier and / or at least one link identifier, the first network device of the multi-link network device saves it locally or in other multi-link network devices associated with the local area; after the multi-link terminal device completes the communication with the multi-link network device, it disconnects through the disassociation and de-authentication process. During the second connection process, on the second link, i.e., the link connecting the second network device and the second terminal device, the multi-link terminal device sends an identifiable management frame that may carry the second link identifier to the multi-link network device; on the second link, after receiving the management frame, the multi-link network device generates a corresponding management frame response; on the first link, i.e., the link connecting the first network device and the first terminal device, the multi-link terminal device sends an identifiable management frame that may carry the first link identifier to the multi-link network device; on the first link, after receiving the management frame, the multi-link network device generates a corresponding management frame response. response); on the first or second link, the multi-link terminal device sends an authentication (Authentication) and (re)association ((re)Association) frame carrying the terminal identifier to the multi-link network device; after receiving the authentication and (re)association frame carrying the terminal identifier, the multi-link network device retrieves the corresponding terminal identifier information on the corresponding link and responds; during the four-way handshake process, the multi-link network device indicates whether the multi-link terminal device can be identified by the terminal identifier, and the frame sent by the multi-link terminal device to the multi-link network device includes but is not limited to the new terminal identifier and / or at least one new link identifier.

[0248] It can be understood that, referring to FIG. 19 , the terminal identifier and / or at least one link identifier are generated by the multi-link network device; before step S210 , the communication method provided in the embodiment of the present application further includes but is not limited to the following steps:

[0249] Step S260: The multi-link network device sends a terminal identifier and / or at least one link identifier to the multi-link terminal device via a third frame.

[0250] It should be noted that before the multi-link network device receives the first frame sent by the multi-link terminal device, the terminal identifier and / or at least one link identifier is sent to the multi-link terminal device through the third frame. The terminal identifier and / or at least one link identifier are generated by the multi-link network device. The sending of the third frame enables the multi-link network device and the multi-link terminal device to have the same terminal identifier and link identifier, which facilitates the multi-link network device to identify the terminal identifier and link identifier later.

[0251] It can be understood that the third frame includes at least one of the following: the third authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; the (re)association response frame in the FILS process between the multi-link terminal device and the multi-link network device; the second authentication frame in the PASN three-way handshake process between the multi-link terminal device and the multi-link network device.

[0252] It should be noted that the four-way handshake protocol is used to negotiate unicast keys. Its main purpose is to ensure that the keys obtained by the applicant and the authenticator are the same and up-to-date. The required pairwise transient key (PTK) can be generated through the four-way handshake. The specific process is as follows: The multi-link network device sends the first authentication frame in the four-way handshake to the multi-link terminal device. The multi-link terminal device sends the second authentication frame in the four-way handshake to the multi-link network device. Upon receiving the second authentication frame in the four-way handshake, the multi-link network device generates the PTK on the multi-link network device side and responds with the third authentication frame in the four-way handshake to the multi-link terminal device. Upon receiving the third authentication frame in the four-way handshake, the multi-link terminal device generates the PTK on the multi-link terminal device side and responds with the fourth authentication frame in the four-way handshake to the multi-link network device. Therefore, the third frame includes the third authentication frame in the four-way handshake between the multi-link terminal device and the multi-link network device.

[0253] It should be noted that the (re)association response frame corresponds to the (re)association request frame.

[0254] It should be noted that, referring to Figure 15, during the first connection process, the first terminal device in the multi-link terminal device discovers the multi-link network device that supports the multi-link operation technology by receiving a beacon and / or a probe response frame; the multi-link terminal device and the multi-link network device complete the multi-link authentication and connection through the multi-link authentication and connection process; during the four-way handshake process, the frame sent by the first network device of the multi-link network device to the first terminal device contains a terminal identifier and / or at least one link identifier, and the frame is the second frame. After the first terminal device of the multi-link terminal device receives the terminal identifier and / or at least one link identifier, it saves it locally or in other multi-link network devices associated with the local area; after the multi-link terminal device completes the communication with the multi-link network device, it disconnects through the disassociation and de-authentication process. During the second connection process, on the second link, i.e., the link connecting the second network device and the second terminal device, the multi-link terminal device sends an identifiable management frame that may carry the second link identifier to the multi-link network device; on the second link, after receiving the management frame, the multi-link network device generates a corresponding management frame response; on the first link, i.e., the link connecting the first network device and the first terminal device, the multi-link terminal device sends an identifiable management frame that may carry the first link identifier to the multi-link network device; on the first link, after receiving the management frame, the multi-link network device generates a corresponding management frame response. response); on the first or second link, the multi-link terminal device sends an authentication (Authentication) and (re)association ((re)Association) frame carrying the terminal identifier to the multi-link network device; after receiving the authentication and (re)association frame carrying the terminal identifier, the multi-link network device retrieves the corresponding terminal identifier information on the corresponding link and responds; during the four-way handshake process, the multi-link network device indicates whether the multi-link terminal device can be identified by the terminal identifier, and the frame sent by the multi-link network device to the multi-link terminal device includes but is not limited to the new terminal identifier and / or at least one new link identifier.

[0255] It can be understood that the first frame is an access network query protocol ANQP request frame, and the fourth frame includes one or more pieces of recommended connection multi-link network device information and link information corresponding to each piece of recommended connection multi-link network device information.

[0256] It should be noted that the multi-link terminal device sends an ANQP request frame (ANQP neighbor query) to the multi-link network device. The multi-link network device can implement access control (Access Control) based on the terminal identifier or link identifier provided by the multi-link network device. Specifically, the multi-link terminal device sends an ANQP request frame including a terminal identifier and / or at least one link identifier to the multi-link network device. The multi-link network device identifies the terminal identifier and / or at least one link identifier in the ANQP request frame, thereby implementing a multi-link connection with the multi-link terminal device.

[0257] It can be understood that the first frame is a connection request frame; the fourth frame contains one or more of the following information: link indication information allowing link establishment, the number of links allowed to establish link connections, whether the link requested for connection is allowed to establish a connection, and whether the terminal device requested for connection is allowed to establish a connection.

[0258] It should be noted that the multi-link network device identifies the terminal identifier and / or at least one link identifier of the first frame, i.e., the connection request frame, determines whether it is the same as the existing terminal identifier and link identifier, and generates a fourth frame. The fourth frame includes one or more of the following information: link indication information allowing link establishment, the number of links allowed to establish link connections, whether the link requested to be connected is allowed to establish a connection, and whether the terminal device requesting to be connected is allowed to establish a connection.

[0259] In addition, referring to Figure 20, an embodiment of the present application also provides an electronic device, including one or more processors; a memory, on which one or more programs are stored, when the one or more programs are executed by one or more processors, the one or more processors implement: the communication method as described in steps S110 to S120, or the communication method as described in steps S210 to S220.

[0260] The processor and the memory may be connected via a bus or other means.

[0261] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor 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.

[0262] The non-transient software programs and instructions required to implement the communication methods of the above embodiments are stored in the memory. When executed by the processor, the communication methods of the above embodiments are executed, for example, the communication methods described in method steps S110 to S120 in Figure 2 described above are executed, or the communication methods described in method steps S210 to S220 in Figure 16 described above are executed.

[0263] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.

[0264] In addition, one embodiment of the present application further provides a computer-readable storage medium, which stores computer-executable instructions. The computer-executable instructions are executed by a processor or controller, enabling the above-mentioned processor to execute the communication method in the above-mentioned embodiment.

[0265] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage media, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0266] The embodiments of the present application have been described in detail above with reference to the accompanying drawings. However, the present application is not limited to the above embodiments. Various modifications can be made within the scope of knowledge possessed by ordinary technicians in the relevant technical field without departing from the purpose of the present application. In addition, the embodiments of the present application and the features of the embodiments can be combined with each other unless there is a conflict.

Claims

1. A communication method, the method comprising: The multi-link terminal device obtains a pre-configured terminal identifier and / or at least one link identifier; The multi-link terminal device sends a first frame to a multi-link network device, wherein the first frame includes the terminal identifier and / or at least one link identifier, so that the multi-link network device identifies the multi-link terminal device and / or the link according to the terminal identifier and / or at least one link identifier.

2. The method according to claim 1, further comprising: The multi-link terminal device receives a fourth frame sent by the multi-link network device, where the fourth frame is a response frame to the first frame.

3. The method according to claim 2, wherein: The first frame and / or the fourth frame comprises a first target field, the terminal identifier comprises a device identifier, the first target field comprises a device identifier information field, and the terminal identifier and / or at least one of the link identifiers are located in the device identifier information field.

4. The method according to claim 3, wherein: The first target field also includes a device identification recognition status field, and the device identification recognition status field is used to indicate whether the device identification of the multi-link terminal device is recognized.

5. The method according to claim 4, wherein: The first target field also includes a device identification control bitmap field, and the device identification control bitmap field includes one or more of the following fields: A device identification status tag, used to indicate whether the first target field includes the device identification status field; A device identification tag, used to indicate whether the device identification information field contains the device identification; A plurality of link tags, each used to indicate whether the device identification information field contains the corresponding link identifier; The device identifier and the link identifier share an indicator tag, which is used to indicate whether the device identifier and the link identifier have the same value.

6. The method according to claim 3, wherein: The device identification information field includes a length field and a device identification field.

7. The method according to claim 3, wherein: The first frame and the fourth frame respectively include a media access control MAC header and a frame body, the first target field is located in the MAC header or the frame body, and the first target field is a device identification element field or a device identification key data encapsulation field.

8. The method according to claim 2, wherein: The first frame and / or the fourth frame comprises a second target field, the terminal identifier comprises an identifiable random media access control address IRM, the second target field comprises an IRM field, the terminal identifier and / or at least one of the link identifiers are located in the IRM field.

9. The method according to claim 8, wherein: The second target field also includes an IRM identification status field, and the IRM identification status field is used to indicate whether the IRM of the multi-link terminal device is identified.

10. The method according to claim 9, wherein: The second target field also includes an IRM control bitmap field, and the IRM control bitmap field includes one or more of the following fields: An IRM identification status tag, used to indicate whether the second target field includes the IRM identification status field; An IRM tag is used to indicate whether the IRM field contains the IRM; A plurality of link tags, each used to indicate whether the IRM field contains the corresponding link identifier; The IRM and the link identifier share an indicator tag, which is used to indicate whether the IRM and the link identifier have the same value.

11. The method according to claim 8, wherein: The first frame and the fourth frame include a media access control MAC header and a frame body, respectively. The second target field is located in the MAC header or the frame body. The second target field is an IRM element field or an IRM key data encapsulation field.

12. The method according to claim 1, wherein: The terminal identifier and / or at least one of the link identifiers are generated by the multi-link terminal device; Before the multi-link terminal device sends the first frame to the multi-link network device, the method further includes: The multi-link terminal device sends the terminal identifier and / or at least one of the link identifiers to the multi-link network device through a second frame.

13. The method according to claim 12, wherein: The second frame includes at least one of the following: A second authentication frame in a four-way handshake process between the multi-link terminal device and the multi-link network device; The fourth authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; A (re)association request frame of the multi-link terminal device and the multi-link network device during the process of establishing a FILS fast initial connection; The multi-link terminal device and the multi-link network device securely negotiate the first authentication frame in the PASN three-way handshake process before connection; The third authentication frame in the PSAN three-way handshake process between the multi-link terminal device and the multi-link network device.

14. The method according to claim 1, wherein: The terminal identifier and / or at least one of the link identifiers are generated by the multi-link network device; Before the multi-link terminal device acquires a pre-configured terminal identifier and / or at least one link identifier, the method further includes: The multi-link terminal device receives a third frame sent by the multi-link network device; The multi-link terminal device obtains the terminal identifier and / or at least one of the link identifiers from the third frame.

15. The method according to claim 14, wherein: The third frame includes at least one of the following: The third authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; (re)association response frame of the multi-link terminal device and the multi-link network device in the FILS process; The second authentication frame between the multi-link terminal device and the multi-link network device in the PASN three-way handshake process.

16. The method according to claim 2, wherein: The first frame is an access network query protocol ANQP request frame, and the fourth frame includes one or more recommended connection multi-link network device information and link information corresponding to each piece of recommended connection multi-link network device information.

17. The method according to claim 2, wherein: The first frame is a connection request frame; The fourth frame includes one or more of the following information: link indication information allowing link establishment, the number of links allowed to establish link connections, whether the link requested to be connected is allowed to establish a connection, and whether the terminal device requested to be connected is allowed to establish a connection.

18. A communication method, the method comprising: The multi-link network device receives a first frame sent by a multi-link terminal device, wherein the first frame includes a terminal identifier and / or at least one link identifier; The multi-link network device identifies the multi-link terminal device and the link according to the terminal identifier and / or at least one of the link identifiers.

19. The method according to claim 18, further comprising: The multi-link network device sends a fourth frame to the multi-link terminal device, where the fourth frame is a response frame to the first frame.

20. The method according to claim 19, wherein: The first frame and / or the fourth frame comprises a first target field, the terminal identifier comprises a device identifier, the first target field comprises a device identifier information field, and the terminal identifier and / or at least one of the link identifiers are located in the device identifier information field.

21. The method according to claim 20, wherein: The first target field also includes a device identification recognition status field, and the device identification recognition status field is used to indicate whether the device identification of the multi-link terminal device is recognized.

22. The method according to claim 21, wherein: The first target field also includes a device identification control bitmap field, and the device identification control bitmap field includes one or more of the following fields: A device identification status tag, used to indicate whether the first target field includes the device identification status field; A device identification tag, used to indicate whether the device identification information field contains the device identification; A plurality of link tags, each used to indicate whether the device identification information field contains the corresponding link identifier; The device identifier and the link identifier share an indicator tag, which is used to indicate whether the device identifier and the link identifier have the same value.

23. The method according to claim 20, wherein: The device identification information field includes a length field and a device identification field.

24. The method according to claim 20, wherein: The first frame and the fourth frame include a media access control MAC header and a frame body respectively, the first target field is located in the MAC header or the frame body, and the first target field is a device identification element field or a device identification key data encapsulation field.

25. The method of claim 19, wherein: The first frame and / or the fourth frame comprises a second target field, the terminal identifier comprises an identifiable random media access control address IRM, the second target field comprises an IRM field, the terminal identifier and / or at least one of the link identifiers are located in the IRM field.

26. The method according to claim 25, wherein: The second target field also includes an IRM identification status field, and the IRM identification status field is used to indicate whether the IRM of the multi-link terminal device is identified.

27. The method according to claim 26, wherein: The second target field also includes an IRM control bitmap field, and the IRM control bitmap field includes one or more of the following fields: An IRM identification status tag, used to indicate whether the second target field includes the IRM identification status field; An IRM tag is used to indicate whether the IRM field contains the IRM; A plurality of link tags, each used to indicate whether the IRM field contains the corresponding link identifier; The IRM and the link identifier share an indicator tag, which is used to indicate whether the IRM and the link identifier have the same value.

28. The method according to claim 25, wherein: The first frame and the fourth frame include a media access control MAC header and a frame body, respectively. The second target field is located in the MAC header or the frame body. The second target field is an IRM element field or an IRM key data encapsulation field.

29. The method of claim 18, wherein: The terminal identifier and / or at least one of the link identifiers are generated by the multi-link terminal device; Before the multi-link network device receives a first frame sent by a multi-link terminal device, the method further includes: The multi-link network device receives a second frame sent by the multi-link terminal device; The multi-link network device obtains the terminal identifier and / or at least one of the link identifiers from the second frame.

30. The method of claim 29, wherein: The second frame includes at least one of the following: A second authentication frame in a four-way handshake process between the multi-link terminal device and the multi-link network device; The fourth authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; A (re)association request frame of the multi-link terminal device and the multi-link network device during the process of establishing a FILS fast initial connection; The multi-link terminal device and the multi-link network device securely negotiate the first authentication frame in the PASN three-way handshake process before connection; The third authentication frame in the PSAN three-way handshake process between the multi-link terminal device and the multi-link network device.

31. The method of claim 18, wherein: The terminal identifier and / or at least one of the link identifiers are generated by the multi-link network device; Before the multi-link network device receives a first frame sent by a multi-link terminal device, the method further includes: The multi-link network device sends the terminal identifier and / or at least one of the link identifiers to the multi-link terminal device via a third frame.

32. The method according to claim 31, wherein: The third frame includes at least one of the following: The third authentication frame in the four-way handshake process between the multi-link terminal device and the multi-link network device; (re)association response frame of the multi-link terminal device and the multi-link network device in the FILS process; The second authentication frame between the multi-link terminal device and the multi-link network device in the PASN three-way handshake process.

33. The method of claim 19, wherein: The first frame is an access network query protocol ANQP request frame, and the fourth frame includes one or more recommended connection multi-link network device information and link information corresponding to each piece of recommended connection multi-link network device information.

34. The method of claim 19, wherein: The first frame is a connection request frame; The fourth frame includes one or more of the following information: link indication information allowing link establishment, the number of links allowed to establish link connections, whether the link requested to be connected is allowed to establish a connection, and whether the terminal device requested to be connected is allowed to establish a connection.

35. An electronic device comprising: one or more processors; A memory having one or more programs stored thereon, when the one or more programs are executed by the one or more processors, the one or more processors implement: The communication method according to any one of claims 1 to 17; or, A communication method as described in any one of claims 18 to 34.

36. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the program implements: The communication method according to any one of claims 1 to 17; or, A communication method as described in any one of claims 18 to 34.

Images