Communication methods, devices, and storage media

Abstract

This application belongs to the technical field of communications. Communication methods, devices, and storage media are disclosed. The method includes a multilink terminal device obtaining a pre-configured terminal identifier and / or at least one link identifier, the multilink terminal device transmitting a first frame containing the terminal identifier and / or at least one link identifier to a multilink network device, thereby allowing the multilink network device to identify the multilink terminal device and / or link according to the terminal identifier and / or at least one link identifier.

Description

Technical Field

[0001] Cross - reference to related applications This application is filed based on Chinese Patent Application No. 2023109210447 filed on July 24, 2023, the entire content of which is incorporated herein by reference, and claims the priority of the Chinese patent application.

[0002] Technical Field This application relates to the field of communication technologies, and in particular, to communication methods, devices, and storage media.

Background Art

[0003] Background During the communication process, a terminal device typically uses a unique fixed Media Access Control (MAC) address to establish a connection with a network device. Identification and authentication technologies based on the device's fixed MAC address are widely used in the field of wireless transmission. However, the fixed MAC address can be easily sniffed by third - party devices using MAC address sniffing to track and locate the connection between the terminal device and the network device. To solve this problem, in some related technical approaches, users are allowed to use a Random MAC Address (RMA) before the terminal device accesses the network device. However, the random MAC address technology of the terminal device causes disruptions to the device MAC - address - related functions defined by the Wi - Fi Alliance (WFA) and the Wi - Fi Broadband Alliance (WBA), resulting in disruptions to the network management of the device.

Summary of the Invention

Means for Solving the Problems

[0004] Summary Methods, network devices, and storage media for communication in various embodiments of this application are provided.

[0005] A method for communication is provided according to a first aspect of this application. The method includes a multilink terminal device obtaining a pre-configured terminal identifier and / or at least one link identifier, and the multilink terminal device transmitting a first frame containing the terminal identifier and / or at least one link identifier to a multilink network device, causing the multilink network device to identify the multilink terminal device and / or at least one link according to the terminal identifier and / or at least one link identifier.

[0006] A second aspect of this application provides a method for communication. The method includes a multilink network device receiving a first frame transmitted by a multilink terminal device, wherein the first frame includes a terminal identifier and / or at least one link identifier, and the multilink network device identifying the multilink terminal device and the link according to the terminal identifier and / or at least one link identifier.

[0007] According to a third aspect of this application, an electronic device is provided. The device includes at least one processor and a memory for storing at least one program which, when executed by the processor, causes the processor to perform the method described in the first aspect or the method described in the second aspect.

[0008] A fourth aspect of this application provides a computer-readable medium that stores a computer program which, when executed by a processor, causes the processor to perform either the method described in the first aspect or the method described in the second aspect.

[0009] According to various embodiments of this application, a multilink terminal device is pre-configured with a terminal identifier and / or at least one link identifier. Before communication is ready, the multilink terminal device transmits a first frame carrying the terminal identifier or at least one link identifier to a multilink network device. The multilink network device identifies the multilink terminal device and link according to the terminal identifier or at least one link identifier, thereby establishing a corresponding link with the multilink terminal device. Thus, different network access services are provided to the multilink terminal device. A multilink connection is achieved between the multilink terminal device and the multilink network device. As a result, network management corresponding to that of the multilink network device can be performed for the multilink terminal device, and communication security is improved. According to various embodiments of this application, the multilink network device is enabled to identify the multilink terminal device and link through the setting of a terminal identifier and / or at least one link identifier, thereby enabling the establishment of a multilink connection between the multilink terminal device and the multilink network device. The multilink network device is enabled to provide the multilink terminal device with corresponding network access services based on the connection and to manage the multilink terminal device. In addition, setting terminal identifiers and link identifiers can reduce sniffing and tracking by third-party devices and improve communication security.

[0010] Further aspects and advantages of this application are partially described in the following description, partially apparent from the following description, or can be acquired by practicing the present disclosure. [Brief explanation of the drawing]

[0011] Brief explanation of the drawing To illustrate the technical methods in the embodiments of this application, some drawings relating to the description of embodiments or related technologies are briefly presented below. It is clear that the drawings described below represent only some embodiments of this disclosure. Those skilled in the art can derive other drawings from these drawings without any creative effort.

[0012] [Figure 1] Figure 1 shows a diagram illustrating the system architecture of a system in which a method for a communication method according to one embodiment of this application may be implemented. [Figure 2] Figure 2 shows a flowchart illustrating a method for communication performed in a multilink terminal device according to one embodiment of this application. [Figure 3] Figure 3 shows a flowchart illustrating a method for communication performed in a multilink terminal device according to another embodiment of this application. [Figure 4] Figure 4 shows a schematic diagram illustrating a first target field related to a method for communication according to one embodiment of the present application. [Figure 5] Figure 5 shows a schematic diagram illustrating a first target field related to a method for communication according to another embodiment of the present application. [Figure 6] Figure 6 shows a schematic diagram illustrating a device identifier control bitmap field related to a method for communication according to one embodiment of this application. [Figure 7] Figure 7 shows a schematic diagram illustrating a device identifier information field related to a method for communication according to one embodiment of this application. [Figure 8] Figure 8 shows a schematic diagram illustrating a first frame and a fourth frame related to a method for communication according to one embodiment of the present application. [Figure 9] Figure 9 shows a schematic diagram illustrating a second target field related to a method for communication according to one embodiment of the present application. [Figure 10] Figure 10 shows a schematic diagram illustrating a second target field related to a method for communication according to another embodiment of the present application. [Figure 11] FIG. 11 depicts a schematic diagram showing an IRM control bit map field related to a method for communication according to an embodiment of the present application. [Figure 12] FIG. 12 depicts a flowchart showing generation of a terminal identifier and / or at least one link identifier in a multi-link terminal device in a method for communication according to an embodiment of the present application. [Figure 13] FIG. 13 depicts a schematic diagram showing communication between a multi-link terminal device and a multi-link network device according to an embodiment of the present application. [Figure 14] FIG. 14 depicts a flowchart showing generation of a terminal identifier and / or at least one link identifier in a multi-link terminal device in a method for communication according to another embodiment of the present application. [Figure 15] FIG. 15 depicts a schematic diagram showing communication between a multi-link terminal device and a multi-link network device according to another embodiment of the present application. [Figure 16] FIG. 16 depicts a flowchart showing a method for communication performed in a multi-link network device according to an embodiment of the present application. [Figure 17] FIG. 17 depicts a flowchart showing a method for communication performed in a multi-link network device according to another embodiment of the present application. [Figure 18] FIG. 18 depicts a flowchart showing generation of a terminal identifier and / or at least one link identifier in a multi-link network device in a method for communication according to an embodiment of the present application. [Figure 19] FIG. 19 depicts a flowchart showing generation of a terminal identifier and / or at least one link identifier in a multi-link network device in a method for communication according to another embodiment of the present application. [Figure 20] FIG. 20 depicts a schematic diagram showing an electronic device to which a method for communication according to an embodiment of the present application is applied.

MODE FOR CARRYING OUT THE INVENTION

[0013] Detailed Description The objectives, technical solutions, and advantages of the present invention can become clear through the following descriptions of various embodiments in conjunction with the drawings. It should be understood that the embodiments described in this specification are illustrative rather than limiting the present invention.

[0014] It should be noted that in some cases, the illustrated or described operations may be performed in an order different from the logical order shown in the flowchart. The terms "first" and "second" are intended to distinguish similar objects when used in this specification, the claims, and the drawings, and do not necessarily mean a specific order or sequence.

[0015] It should also be understood that references to "one embodiment" or "some embodiments" and the like described in the descriptions of some embodiments of this application mean that the specific features, structures, or characteristics described in relation to this embodiment are included in one or more embodiments of this application. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," and "in further embodiments" that appear in different parts of this specification do not necessarily all refer to the same embodiment, and unless otherwise emphasized, they mean "not all but one or more embodiments." The terms "comprise," "include," "have," and their variants mean, unless otherwise specified, all "include but are not limited to ~."

[0016] In the description of embodiments of this application, terms such as “greater than,” “less than,” and “more than” are to be understood as excluding the numbers mentioned, while terms such as “above,” “below,” and “within” are to be understood as including the numbers mentioned. The terms “first” and “second,” where mentioned, are intended to distinguish technical features and should not be understood as indicating or implying relative importance, or implicitly indicating the number or order of the technical features shown. Descriptions of orientations such as “up,” “down,” “forward,” “backward,” “left,” and “right” should be understood as indicating orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are merely for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the mentioned device or component has a particular orientation or must be configured and operated in a particular orientation. Accordingly, these terms should not be understood as limitations on this application.

[0017] In the description of the various embodiments of this application, terms such as providing, installing, or connecting should be understood broadly unless otherwise specified, and those skilled in the art can reasonably determine the specific meaning of such terms in the various embodiments of this disclosure in conjunction with the specific content of the technical method.

[0018] During communication, terminal devices typically use a unique, fixed MAC address to establish a connection with network equipment. Identification and authentication techniques based on device fixed MAC addresses are widely used in the field of wireless transmission. However, the use of fixed MAC addresses allows third-party devices to use MAC address sniffing techniques to track and locate the connection between terminal devices and network devices. Wireless network technologies, for example, incorporate multi-link operation (MLO) technology. In MLO, MAC addresses include link-specific MAC addresses and multi-link device MAC addresses (MLD MAC addresses). Based on the differences in the MAC address information carried, frames used for multi-link terminal device identification are typically divided into three categories: frames carrying only the link-specific MAC address, frames carrying both the current link-specific MAC address and the MLD MAC address, and frames carrying the current link-level MAC address, another link-specific MAC address, and the MLD MAC address. Third-party devices can track and locate the communication process based on the link-specific MAC address and the MLD MAC address.

[0019] To address this issue, several related technical schemes allow users to use random MAC addresses (RMAs) before terminal devices access network devices. However, random MAC address technology for terminal devices causes malfunctions in device MAC address-related functions defined by the Wi-Fi Alliance (WFA) and Wi-Fi Broadband Alliance (WBA), leading to disruptions in the network management of devices.

[0020] With this in mind, embodiments of the present application provide a method for communication, a network device, and a storage medium. In the methods according to various embodiments of the present application, a multilink network device can establish a multilink connection between a multilink terminal device and a multilink network device by identifying the multilink terminal device and the link through the setting of a terminal identifier and / or at least one link identifier. The multilink network device is enabled to provide the multilink terminal device with corresponding network access services based on the connection and to manage the multilink terminal device. In addition, the setting of terminal identifiers and link identifiers can reduce sniffing and tracking by third-party devices and improve communication security.

[0021] Several embodiments of this application will be described in conjunction with the drawings.

[0022] Figure 1 shows a diagram illustrating a system architecture of a system in which a method for a communication method according to one embodiment of this application may be implemented. The system architecture includes multilink terminal devices and multilink network devices.

[0023] A multilink network device is a device configured to receive a first frame transmitted by one or more multilink terminal devices, and can identify multilink terminal devices and links according to a terminal identifier and / or at least one link identifier. The multilink network device is configured to wirelessly connect with multilink terminal devices for data transfer.

[0024] Multilink network devices, also known as wireless access points, are essential devices in wireless local area networks. They can receive signals from wired networks and transmit those signals wirelessly, thereby enabling wireless connection of multilink terminal devices to the network. In addition, multilink network devices allow connection to multiple terminal devices, providing high-speed and stable network services. The operating principle of wireless network access devices is to convert wired network signals into wireless signals and transmit data via wireless signals. In a wireless network, wireless network access devices function as relay stations, receiving data from wireless devices and then transmitting that data to the wired network. Simultaneously, wireless network access devices can also receive data from wired networks, convert that data into wireless signals, and transmit them to wireless devices.

[0025] A multilink terminal device is a device configured to acquire a pre-configured terminal identifier and / or at least one link identifier and to transmit a first frame to a multilink network device. The multilink terminal device can establish a communication connection with a multilink network device for data transfer. Multiple links can be established between the multilink terminal device and the multilink network device as needed.

[0026] It should be noted that each multilink terminal device and multilink network device includes three links: 2.4GHz, 5GHz, and 6GHz. Multilink terminal devices and multilink network devices can complete the authentication, connection, and four-way handshake process via the 2.4GHz link through Association Request and Association Response frames, thereby achieving multilink connectivity and enabling data transmission over the three links at 2.4GHz, 5GHz, and 6GHz.

[0027] It should be noted that multilink terminal devices and multilink network devices can achieve multilink connectivity. The application system shown in Figure 1 is only a schematic diagram. A multilink connection between a multilink terminal device and a multilink network device includes the connection of at least one link.

[0028] It should be noted that "multilink terminal device" and "multilink network device" are merely general terms. In actual communication processes, multiple multilink terminal devices and multiple multilink network devices may be provided.

[0029] The system architecture and application scenario described in one embodiment of this application are intended for better understanding, rather than as a limitation on the technical methods of the various embodiments of this application. As system architectures evolve and new application scenarios emerge, it is known to those skilled in the art that the technical methods provided by the embodiments of this disclosure are also applicable to similar technical problems.

[0030] The system architecture shown in Figure 1 is not intended to limit the embodiments of this application and it will be understood by those skilled in the art that it may include more or fewer components than those shown, or that some components may be combined, or that it may have different arrangements of components.

[0031] In the system architecture shown in Figure 1, each unit can invoke the communication program stored therein and implement a method for communication.

[0032] Various embodiments of the method for the communication method of this application are proposed based on the system architecture described above.

[0033] Figure 2 shows a flowchart illustrating a method for communication in a multilink terminal device according to one embodiment of this application. According to a non-limiting embodiment, the communication method includes the following operations.

[0034] In operation S110, the multilink terminal device obtains a pre-configured terminal identifier and / or at least one link identifier.

[0035] In operation S120, the multilink terminal device transmits a first frame to the multilink network device. The first frame includes a terminal identifier and / or at least one link identifier to enable the multilink network device to identify the multilink terminal device and / or the link according to the terminal identifier and / or at least one link identifier.

[0036] In some implementations, a multilink terminal device obtains a pre-configured terminal identifier and / or at least one link identifier. The terminal identifier corresponds to the multilink terminal device, and each link identifier corresponds to each of the multiple links. The multilink terminal device sends a first frame to a multilink network device. The first frame contains the terminal identifier and / or at least one link identifier. The multilink network device identifies the multilink terminal device and / or links via the terminal identifier and / or at least one link identifier. This establishes a multilink connection, enabling simultaneous data transmission across multiple links. Corresponding network access services are provided to each multilink terminal device based on the multilink connection. The multilink terminal devices are managed. In addition, the configuration of terminal identifiers and link identifiers can reduce sniffing and positioning by third-party devices, improving connection security.

[0037] In one embodiment, a multilink network device identifies a multilink terminal device and / or a link via a terminal identifier and / or at least one link identifier, and feeds back the identification result information to the multilink terminal device. The multilink network device provides feedback to the multilink terminal device when the multilink terminal device and / or the link of the multilink terminal device have been successfully identified by the multilink network device. As a result, the multilink terminal device can send a connection request to the multilink network device to establish a multilink connection between the multilink network device and the multilink terminal device in order to enable simultaneous data transmission over multiple links. The establishment of a multilink connection can enable the network access service corresponding to the multilink terminal device.

[0038] It should be noted that multilink connections enable simultaneous data transmission between multilink network devices and multilink terminal devices via multiple links, thereby improving data transmission throughput, reducing data transmission latency, and thus improving communication efficiency.

[0039] It should be noted that a terminal identifier corresponds to one of several multilink terminal devices. A multilink network device can identify a multilink terminal device based on its terminal identifier. Each of at least one link identifier corresponds to each of several links for connecting to a multilink terminal device. A multilink network device can identify each link based on one of its link identifiers, thereby establishing each link connection with a multilink terminal device.

[0040] In multilink operation technology, it should be noted that MAC addresses can include link-specific MAC addresses and multilink device (MLD) MAC addresses. A multilink terminal device typically has a unique MLD MAC address and at least one link-specific MAC address. The MLD MAC address uniquely identifies the multilink terminal device. Thus, a multilink terminal device corresponds to a link identifier, and a multilink network device can identify a single corresponding multilink terminal device through the link identifier. In addition, while the link-specific MAC addresses of a single multilink terminal device may be different, one of the link-specific MAC addresses of a multilink terminal device may be the same as the MLD MAC address. Therefore, the link identifiers corresponding to multiple links of a single multilink terminal device may be different, and one of the link identifiers may be the same as the terminal identifier. If the frame used for identifying a multilink terminal device carries only the link-specific MAC address, the first frame carries only the link identifier; if the link identifier is the same as the terminal identifier, the first frame carries either the terminal identifier or the link identifier. If the frame used for multilink terminal device identification carries the link-specific MAC address and MLD MAC address of the current link, the first frame carries one terminal identifier and one link identifier. If the frame used for multilink terminal device identification carries the link-specific MAC address of the current link, the link-specific MAC address of another link, and the MLD MAC address, the first frame carries a terminal identifier and multiple link identifiers.

[0041] It should be noted that terminal identifiers and link identifiers may be composed of multilink terminal devices or multilink network devices.

[0042] It should be noted that the first frame is encrypted and transmitted between the multilink terminal device and the multilink network device. Therefore, it is not easy, if not impossible, for a third-party device to sniff and track the terminal identifier and link identifier transmitted by the first frame, thereby improving communication security.

[0043] It should be noted that before a multilink terminal device transmits a first frame to a multilink network device, the multilink network device receives the terminal identifier and / or at least one link identifier transmitted by the multilink terminal device and stores the terminal identifier and / or at least one link identifier locally or in another multilink network device associated with the local area. The terminal identifier and link identifier correspond to those carried in the first frame so that the multilink network device can subsequently identify the terminal identifier and link identifier.

[0044] It should be noted that the first frame is a frame sent by a multilink terminal device to a multilink network device. Typically, the frame is intended to request a connection with the multilink network device. For example, the first frame may be an association request frame in Fast Initial Link Setup (FILS) mode.

[0045] It should be noted that encrypted transmission of the first frame can be achieved via keys. In one embodiment, a multilink terminal device and a multilink network device generate a multilink operation-specific pairwise transient key (PTK) and a link-specific group transient key (GTK) via a four-way handshake on the link, which are used to encrypt and decrypt transmitted unicast and multicast data frames, respectively, to ensure the security of data transmission.

[0046] Referring to Figure 3, according to a non-limiting embodiment, the method for a communication method further includes the following operations.

[0047] In operation S130, the multilink terminal device receives a fourth frame transmitted by the multilink network device. The fourth frame is a response frame to the first frame.

[0048] After receiving the first frame, the multilink network device should note that it identifies the terminal identifier and link identifier to determine whether the same terminal identifier and link identifier are stored locally within the multilink network device or within the network associated with the multilink network device. The multilink network device then generates a fourth frame based on this determination and transmits the fourth frame to the multilink 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 within the multilink network device or within the network associated with the local network, the multilink terminal device establishes a multilink connection with the multilink network device and transmits data. Otherwise, the establishment of a connection between the multilink terminal device and the multilink network device fails.

[0049] Referring to Figures 4 and 5, one or both of the first and fourth frames include a first target field. The terminal identifier includes a device identifier. The first target field includes a device identifier information field that includes the terminal identifier and / or at least one link identifier.

[0050] It should be noted that the terminal identifier of a multilink terminal device can be the device ID, which is the device ID of the multilink terminal device. A multilink network device can obtain the ID of a multilink terminal device by identifying the device ID.

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

[0052] In one embodiment, the first frame and the fourth frame each include a first target field schematically shown with reference to Figure 4 or Figure 5. The first target field includes a device identifier information field (device ID information), in which a terminal identifier and / or at least one link identifier are carried. The device identifier information field may carry multiple different device identifiers. The number of bytes (octets) in the device identifier information field is variable, and its specific number can be set according to the number of terminal identifiers and link identifiers.

[0053] Referring to Figures 4 and 5, it can be understood that the first target field further includes a device identifier recognition status field indicating whether the device identifier of the multilink terminal device has been recognized.

[0054] It should be noted that the first target field also includes a Device ID Status field, which indicates whether the device identifier of the multilink terminal device is recognized.

[0055] It should be noted that the device identifier recognition status field is designed to occupy 1 bit. A value of "0" in the device identifier recognition status field indicates an unrecognized device identifier for a multilink terminal device. A value of "1" in the device identifier recognition status field indicates a recognized device identifier for a multilink terminal device.

[0056] It should be noted that the fourth frame received by the multilink terminal device is a response frame to the first frame transmitted by the multilink network device. When the multilink network device recognizes the terminal identifier of the multilink terminal device, the value of the device identifier recognition status field is set to "1". In this case, the multilink network device and the multilink terminal device can establish a connection. If the multilink network device cannot recognize the terminal identifier of the multilink terminal device, the value of the device identifier recognition status field is set to "0". In this case, the establishment of a connection between the multilink network device and the multilink terminal device fails.

[0057] In some embodiments, referring to Figures 4 to 6, the first target field is the following field, namely: A device identifier recognition status tag indicating whether the first target field includes a device identifier recognition status field. A device identifier tag that indicates whether the device identifier information field contains a device identifier. Multiple link tags, each indicating whether the device identifier information field contains the corresponding link identifier, and A device and link identifier sharing indicator tag that indicates whether the device identifier and link identifier have the same value. It further includes a device identifier control bitmap field containing one or more of the following.

[0058] It should be noted that the first target field further includes a device ID control bitmap field compatible with multilink operation technology. Setting the device ID control bitmap field provides the basis for multilink connectivity between multilink terminal devices and multilink network devices.

[0059] It should be noted that the Device ID Status tag indicates whether the first target field contains the Device ID Status field. The Device ID Status tag occupies 1 bit. When the value of the Device ID Status tag is "0", it indicates that the first target field does not contain the Device ID Status field. When the value of the Device ID Status tag is "1", it indicates that the first target field contains the Device ID Status field.

[0060] In one embodiment, a multilink terminal device transmits a first frame to a multilink network device. The first frame includes a terminal identifier and / or at least one link identifier, wherein the terminal identifier in the first frame is pre-configured, and the device identifier in the terminal identifier is the device identifier of the multilink terminal device. In this case, the first target field of the first frame does not include a device identifier recognition field, and therefore the value of the device identifier recognition status tag is set to "0" accordingly.

[0061] It should be noted that the fourth frame is a response frame to the first frame. After identifying the multilink terminal device according to the terminal identifier carried in the first frame, the multilink network device generates the fourth frame and transmits it to the multilink terminal device. In this case, the first target field corresponding to the fourth frame includes a device identifier recognition field, and the value of the device identifier recognition status tag is "1".

[0062] In one embodiment, referring to Figure 6, the multiple link tags are the first link tag (1st.link ID), the second link tag (2nd.link ID), and the third link tag (3rd.link ID). Each link tag corresponds to a respective link and indicates whether the device identifier recognition information field contains the link identifier for that link. If the value of the link tag is "1", it indicates that the subsequent device identifier information field contains the corresponding link identifier. If the value of the link tag is "0", it indicates that the device identifier information field does not contain the corresponding link identifier.

[0063] It should be noted that the device identifier control bitmap field shown in Figure 6 has three link tags, namely a first link tag, a second link tag, and a third link tag, each link tag occupying 1 bit. In one embodiment, a multilink terminal device and a multilink network device each include three links, namely a first link, a second link, and a third link. The multilink terminal device and the multilink network device can be connected via any one or more of the three links. Each of the first, second, and third links is assigned its own link identifier. In the first frame, when the value of the link tag is "1", it indicates that the multilink terminal device expects to establish a connection with the multilink network device via the corresponding link. For example, if the values ​​of the first and second link tags in the first target field of the first frame are "1" and the value of the third link tag is "0", it indicates that the device identifier information field contains only the link identifiers corresponding to the first and second links, and that the multilink terminal device expects to establish a connection with the multilink device via the first and second links. In the fourth frame, the value of the link tag in the first target field corresponds to the one carried in the first frame. When the value of the recognition status field is "1", it indicates that the device identifier of the multilink terminal device can be identified by the multilink network device.

[0064] It should be noted that if the multilink network device is successfully identified and can identify the device identifier of the multilink terminal device, the value of the recognition status field in the fourth frame will be set to "1". Based on this, the multilink terminal device can send a connection request to the multilink network device so that the multilink terminal device and the multilink network device can establish a connection between the corresponding links and realize a multilink connection.

[0065] The device identifier control bitmap field in Figure 6 is shown as an example only, and it should be noted that it can provide more or fewer link tags. The number of link tags in the device identifier control bitmap field is determined by the number of links between the multilink terminal device and the multilink network device.

[0066] It should be noted that the device identifier control bitmap field includes a device and link identifier sharing indicator tag, which takes 1 bit and indicates whether the device identifier and link identifier share the same value. In multilink operation technology, one of the link-specific MAC addresses of a multilink terminal device may be the same as the MLD MAC address. Therefore, although the link identifiers corresponding to links of the same multilink terminal device are different, one of the link identifiers may be the same as the terminal identifier. If the device identifier and link identifier are the same, the value of the device and link identifier sharing indicator tag is "1", and otherwise it is "0".

[0067] In one embodiment, the device and link identifier sharing indicator is implicit. Specifically, the communication protocol specifies that the terminal identifier and the link identifier are the same. Therefore, it is not necessary to specifically set the device and link identifier sharing indicator in the first target field under the protocol.

[0068] In one embodiment, referring to Figure 6, the device identifier control bitmap field further includes a reserved tag ("Reserved") occupying 2 bits.

[0069] In one embodiment, referring to Figure 7, the device identifier information field includes a length field and a device identifier field.

[0070] It should be noted that the device identifier information field includes a length field and a device ID field. The device identifier field is intended to store the device identifier of the multilink terminal device, and the length field indicates the bit length of the device identifier of the multilink terminal device.

[0071] In one embodiment, referring to Figure 8, the first frame and the fourth frame each include a Media Access Control (MAC) header and a frame body. The first target field is carried in the MAC header or frame body and is a device identifier element field or a device identifier key data encapsulation field.

[0072] It should be noted that each of the first and fourth frames includes a MAC header and a frame body. The first target field is carried in the frame body or MAC header. The first target field is either a device identifier element field or a device identifier key data encapsulation field.

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

[0074] In one embodiment, referring to Figure 4, the device identifier element field includes an element identifier field (Element ID), a length information field (Length), an element identifier extension field (Element ID Extension), a device identifier control bitmap field (Device ID control bitmap), a device identifier recognition status field (Device ID Status), and a device identifier information field (Device ID information). In one embodiment, the element identifier field, length information field, element identifier information extension field, device identifier control bitmap field, and device identifier recognition status field each occupy 1 byte, and the number of bytes in the device identifier information field is set to be variable.

[0075] In one embodiment, referring to Figure 5, during the transmission of the first and fourth frames, the device identifier element field is typically encrypted for transmission to improve the security of the information transmission. After the device identifier element field is encrypted, a device identifier key data encapsulation field is obtained. The device identifier key data encapsulation field includes a device identifier control bitmap field, a device identifier recognition status field, and a device identifier information field (device ID information). In one embodiment, the device identifier control bitmap field and the device identifier recognition status field each occupy one byte, and the number of bytes in the device identifier information field is set to be variable.

[0076] Referring to Figures 6 and 7, it should be noted that the structure and usage of the device identifier control bitmap field, device identifier recognition state field, and device identifier information field within the device identifier element field and device identifier key data encapsulation field are the same, respectively. The device identifier control bitmap field includes a device identifier recognition state tag, a device identifier tag, multiple link tags, a device and link identifier sharing indicator tag, and a reserved tag. Each device identifier information field includes a length field and a device identifier field.

[0077] In one embodiment, referring to Figures 9 and 10, the first frame and / or the fourth frame include a second target field. The terminal identifier includes an identifiable random MAC (IRM) address (IRMA). The second target field includes an IRM field that carries the terminal identifier and / or at least one link identifier.

[0078] It should be noted that the terminal identifier of a multilink terminal device can be set as an IRMA. IRMA is a media access control address randomly assigned to a multilink terminal device. A multilink network device can obtain the media access control address of a multilink terminal device via its IRMA, thereby establishing a connection with the multilink terminal device.

[0079] It should be noted that link identifiers can also be indicated by IRMA. Each link identifier is assigned a corresponding IRMA.

[0080] In one embodiment, the first frame and the fourth frame each include a second target field schematically shown with reference to Figure 9 or Figure 10. The second target field includes an IRM field. Terminal identifiers and / or at least one link identifier are carried in the IRM field. The IRM field may carry multiple different IRMs. The number of bytes (octets) of the IRM field is 6*N, where "6" is the number of bytes in one IRM and "N" is the total number of terminal identifiers and link identifiers carried by the first frame and / or the fourth frame, i.e., the total number of IRMs. The setting of the number of bytes of the IRM field allows the first frame and / or the fourth frame to carry terminal identifiers and / or at least one link identifier.

[0081] In one embodiment, referring to Figures 9 and 10, the second target field further includes an IRM recognition status field indicating whether the IRM of the multilink terminal device is recognized.

[0082] It should be noted that the second target field also includes an IRM recognition status field (Device ID Status) indicating whether the IRM multilink terminal device has been recognized.

[0083] It should be noted that the IRM recognition status field is designed to occupy 1 bit. A value of "0" in the IRM recognition status field indicates an unrecognized IRM for the multilink terminal device. A value of "1" in the device identifier recognition status field indicates a recognized IRM for the multilink terminal device.

[0084] It should be noted that the fourth frame received by the multilink terminal device is a response frame to the first frame transmitted by the multilink network device. When the multilink network device recognizes the IRM of the multilink terminal device, the value of the IRM recognition status field is set to "1". If the multilink network device cannot recognize the IRM of the multilink terminal device, the value of the IRM recognition status field is set to "0".

[0085] In some embodiments, referring to Figures 9 to 11, the second target field is: The second target field includes an IRM recognition status tag indicating whether it contains an IRM recognition status field. IRM tag indicating whether the IRM field contains IRM. Multiple link tags indicating whether the IRM field carries the corresponding link identifier, and IRM and link identifier sharing indicator tag, which indicates whether the IRM and link identifier share the same value. It further includes an IRM control bitmap field containing one or more of the following.

[0086] It should be noted that the second target field further includes an IRM control bitmap field compatible with multilink operation technology. Setting the IRM control bitmap field provides the basis for multilink connectivity between multilink terminal devices and multilink networks.

[0087] It should be noted that the IRM ID Status tag indicates whether the second target field contains the IRM ID Status field. The IRM ID Status tag occupies 1 bit. If the value of the IRM ID Status tag is "0", it indicates that the second target field does not contain the IRM ID Status field. If the value of the IRM ID Status tag is "1", it indicates that the second target field contains the IRM ID Status field.

[0088] In one embodiment, a multilink terminal device transmits a first frame to a multilink network device. The first frame includes a terminal identifier and / or at least one link identifier, wherein the terminal identifier in the first frame is pre-configured, and the device identifier in the terminal identifier is the device identifier of the multilink terminal device. In this case, the second target field of the first frame does not include an IRM recognition field, and therefore the value of the IRM recognition status tag is correspondingly set to "0".

[0089] It should be noted that the fourth frame is a response frame to the first frame. After identifying the multilink terminal device according to the terminal identifier carried in the first frame, the multilink network device generates the fourth frame and transmits it to the multilink terminal device. In this case, the second target field corresponding to the fourth frame includes an IRM recognition field, and the value of the IRM recognition status tag is "1".

[0090] In one embodiment, referring to Figure 11, the multiple link tags are the first link tag (1st.link ID), the second link tag (2nd.link ID), and the third link tag (3rd.link ID). Each link tag corresponds to a respective link and indicates whether the IRM field contains the link identifier for that link. If the value of a link tag is "1", it indicates that the subsequent IRM field contains the corresponding link identifier. If the value of a link tag is "0", it indicates that the IRM field does not contain the corresponding link identifier.

[0091] It should be noted that the IRM control bitmap field shown in Figure 11 has three link tags, namely a first link tag, a second link tag, and a third link tag, each link tag occupying 1 bit. In one embodiment, a multilink terminal device and a multilink network device each include three links, namely a first link, a second link, and a third link. The multilink terminal device and the multilink network device can be connected via any one or more of the three links. Each of the first, second, and third links is assigned its own link identifier. In the first frame, when the value of the link tag is "1", it indicates that the multilink terminal device expects to establish a connection with the multilink network device via the corresponding link. For example, if the values ​​of the first and second link tags in the second target field of the first frame are "1" and the value of the third link tag is "0", it indicates that the IRM field contains only the link identifiers corresponding to the first and second links, and that the multilink terminal device expects to establish a connection with the multilink device via the first and second links. In the fourth frame, the value of the link tag in the second target field corresponds to the one carried in the first frame. When the value of the recognition status field is "1", it indicates that the IRM of the multilink terminal device can be identified by the multilink network device.

[0092] It should be noted that if the multilink network device is successfully identified and can identify the device identifier of the multilink terminal device, the value of the recognition status field in the fourth frame will be set to "1". Based on this, the multilink terminal device can send a connection request to the multilink network device so that the multilink terminal device and the multilink network device can establish a connection between the corresponding links and realize a multilink connection.

[0093] The IRM control bitmap field in Figure 11 is shown as an example only, and it should be noted that it can provide more or fewer link tags. The number of link tags in the IRM control bitmap field is determined by the number of links between the multilink terminal device and the multilink network device.

[0094] It should be noted that the IRM control bitmap field includes an IRM and link identifier sharing indicator tag, which takes 1 bit and indicates whether the IRM and link identifier share the same value. In multilink operation technology, one of the link-specific MAC addresses of a multilink terminal device may be the same as the MLD MAC address. Therefore, although the link identifiers corresponding to links of the same multilink terminal device are different, one of the link identifiers may be the same as the terminal identifier. If the terminal identifier and IRM corresponding to the link identifier are the same, the value of the IRM and link identifier sharing indicator tag is "1", and otherwise it is "0".

[0095] In one embodiment, the IRM and link identifier sharing indicator are implicit. Specifically, the communication protocol specifies that the terminal identifier and the link identifier are the same. Therefore, it is not necessary to specifically set the IRM and link identifier sharing indicator in the second target field under the protocol.

[0096] In one embodiment, referring to Figure 11, the IRM control bitmap field further includes a reserved tag ("Reserved") occupying 2 bits.

[0097] In one embodiment, referring to Figure 8, the first frame and the fourth frame each include a Media Access Control (MAC) header and a frame body. The second target field is carried in the MAC header or frame body and is an IRM element field or an IRM key data encapsulation field.

[0098] It should be noted that the first and fourth frames include a MAC header and a frame body. The second target field is carried in the frame body or MAC header. The second target field is an IRM element field or an IRM key data encapsulation field.

[0099] It should be noted that if the terminal identifier and link identifier in the second target field are the same, the terminal identifier is carried in the transmitting-side address (TA) or receiving-side address (RA) field of the MAC header. If the terminal identifier and link identifier are different, the terminal identifier is carried in the frame body, and the link identifier is carried in the TA or RA field of the MAC header.

[0100] In one embodiment, referring to Figure 9, the IRM element field includes an Element ID field, a Length information field, an Element ID Extension field, an IRM control bitmap field, an IRM Status field, and an IRM Information field (IRM Information). In one embodiment, the Element ID field, Length information field, Element ID Extension field, IRM control bitmap field, and IRM Status field each occupy 1 byte. The number of bytes in the IRM field is set to 6*N, where N represents the number of IRMs.

[0101] In one embodiment, referring to Figure 10, during the transmission of the first and fourth frames, the IRM element fields are typically encrypted for transmission to improve the security of the information transmission. After the IRM element fields are encrypted, an IRM key data encapsulation field is obtained. The IRM key data encapsulation field includes an IRM control bitmap field, an IRM status field, and an IRM field (IRM information). In one embodiment, the IRM control bitmap field and the IRM status field each occupy 1 byte, and the number of bytes in the IRM field is set to be variable.

[0102] Referring to Figure 11, it should be noted that the structure and usage of the IRM control bitmap field, IRM recognition state field, and IRM information field within the IRM element field and IRM key data encapsulation field are the same, respectively. The IRM control bitmap field includes the IRM recognition state tag, IRM identifier tag, multiple link tags, IRM and link identifier sharing indicator tag, and reserved tag.

[0103] In one embodiment, a terminal identifier and / or at least one link identifier are generated by the multilink terminal device. Referring to Figure 12, according to a non-limiting embodiment, prior to operation S120, the method further includes the following operations.

[0104] In operation S140, the multilink terminal device transmits a terminal identifier and / or at least one link identifier to the multilink network device via a second frame.

[0105] In one embodiment, before transmitting a first frame to a multilink network device, the multilink terminal device transmits a terminal identifier and / or at least one link identifier to the multilink network device via a second frame. The multilink network device stores the terminal identifier and / or at least one link identifier carried by the second frame locally or in another multilink network device associated with the local area, thereby enabling the multilink network device to subsequently identify the terminal identifier and link identifier.

[0106] In one embodiment, the second frame includes at least one of the following: a second authentication frame during a four-way handshake process between a multilink terminal device and a multilink network device; a fourth authentication frame during a four-way handshake process between a multilink terminal device and a multilink network device; a (re)association request frame during a Fast Initial Link Setup (FILS) process between a multilink terminal device and a multilink network device; a first authentication frame during a Pre-Association Security Negotiation (PASN) three-way handshake process between a multilink terminal device and a multilink network device; or a third authentication frame during a PSAN three-way handshake process between a multilink terminal device and a multilink network device.

[0107] It should be noted that the 4-way handshake protocol is intended for unicast key negotiation, and its primary purpose is to ensure that the keys obtained by the applicant and the certifier are the same and up-to-date. The required pairwise transient key (PTK) can be generated by the 4-way handshake, and the process is as follows: The multilink network device sends a first authentication frame to the multilink terminal device during the 4-way handshake. The multilink terminal device sends a second authentication frame to the multilink network device during the 4-way handshake. Upon receiving the second authentication frame during the 4-way handshake, the multilink network device generates a PTK on its end and responds to the multilink terminal device using a third authentication frame during the 4-way handshake. Upon receiving the third authentication frame during the 4-way handshake, the multilink terminal device generates a PTK on its end and responds to the multilink network device using a fourth authentication frame during the 4-way handshake. As a result, the second frame includes the second and fourth authentication frames in the four-way handshake process between the multilink terminal device and the multilink network device.

[0108] In one embodiment, the (re)association request frame of the multilink terminal device and multilink network device during FILS establishment is also a second frame. FILS is primarily intended to accelerate the establishment of connections between multilink terminal devices and multilink network devices. FILS is defined in 802.11ai and allows radio access points, such as multilink network devices, to periodically transmit discovery frames at a shorter 20-millisecond interval compared to the beacon period, enabling multilink terminal devices to discover multilink network devices more quickly. Furthermore, the (re)association in FILS includes Dynamic Host Configuration Protocol (DHCP) information, which allows address configuration to be completed along with the association.

[0109] In one embodiment, the third frame includes a third authentication frame in the PSAN 3-way handshake process between a link terminal device and a multilink network device.

[0110] In one embodiment, referring to Figure 13, during the first connection process, the first terminal device among a plurality of multilink terminal devices discovers a multilink network device that supports multilink operation technology by receiving a beacon and / or probe response frame. The multilink terminal device and the multilink network device complete multilink authentication and connection through a multilink authentication and connection process. During the four-way handshake process, the frame (i.e., the second frame) sent by the first terminal device among the plurality of multilink terminal devices to the first network device includes a terminal identifier and / or at least one link identifier. After receiving the terminal identifier and / or at least one link identifier, the first network device among the multilink network devices stores the identifier locally or in another multilink network device associated with the local area. After completing communication with the multilink network device, the multilink terminal device disconnects through a disassociation and deauthentication process. During the second connection process, the multilink terminal device transmits an identifiable management frame capable of carrying a second link identifier to the multilink network device via the second link, i.e., the link connecting the second network device and the second terminal device. After receiving the management frame via the second link, the multilink network device generates a corresponding management frame response. The multilink terminal device transmits an identifiable management frame capable of carrying a first link identifier to the multilink network device via the first link, i.e., the link connecting the first network device and the first terminal device. After receiving the management frame via the first link, the multilink network device generates a corresponding management frame response. The multilink terminal device transmits an authentication and (re)association frame carrying a terminal identifier to the multilink network device via the first or second link.After receiving an authentication and (re)association frame carrying the terminal identifier, the multilink network device retrieves the corresponding terminal identifier information via the corresponding link and responds. During the 4-way handshake process, the multilink network device indicates whether it can identify the multilink terminal device by the terminal identifier. Frames sent by the multilink terminal device to the multilink network device include, but are not limited to, a new terminal identifier and / or at least one new link identifier.

[0111] In one embodiment, a terminal identifier and / or at least one link identifier is generated by a multilink network device. Referring to Figure 14, according to a non-limiting embodiment, prior to operation S110, the method further includes the following operations.

[0112] In operation S150, the multilink terminal device receives a third frame transmitted by the multilink network device.

[0113] In operation S160, the multilink terminal device obtains a terminal identifier and / or at least one link identifier from the third frame.

[0114] In one embodiment, before obtaining a terminal identifier and / or at least one link identifier, the multilink terminal device receives a third frame transmitted by the multilink 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 multilink network device. Transmitting the third frame allows the multilink network device and the multilink terminal device to have the same terminal identifier and link identifier, thereby facilitating the multilink network device to subsequently identify the terminal identifier and link identifier.

[0115] In one embodiment, the third frame includes at least one of the following: a third authentication frame in a four-way handshake process between a multilink terminal device and a multilink network device; a (re)association response frame in a FILS process between a multilink terminal device and a multilink network device; or a second authentication frame in a PASN three-way handshake process between a multilink terminal device and a multilink network device.

[0116] It should be noted that the 4-way handshake protocol is intended for unicast key negotiation, and its primary purpose is to ensure that the keys obtained by the applicant and the certifier are the same and up-to-date. The required pairwise transient key (PTK) can be generated by the 4-way handshake, and the process is as follows: The multilink network device sends a first authentication frame to the multilink terminal device during the 4-way handshake. The multilink terminal device sends a second authentication frame to the multilink network device during the 4-way handshake. Upon receiving the second authentication frame during the 4-way handshake, the multilink network device generates a PTK on its end and responds to the multilink terminal device using a third authentication frame during the 4-way handshake. Upon receiving the third authentication frame during the 4-way handshake, the multilink terminal device generates a PTK on its end and responds to the multilink network device using a fourth authentication frame during the 4-way handshake. Therefore, the third frame includes a third authentication frame in the four-way handshake process between the multilink terminal device and the multilink network device.

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

[0118] In one embodiment, referring to Figure 15, during the first connection process, the first terminal device among a plurality of multilink terminal devices discovers a multilink network device that supports multilink operation technology by receiving a beacon and / or probe response frame. The multilink terminal device and the multilink network device complete multilink authentication and connection through a multilink authentication and connection process. During the four-way handshake process, a frame (i.e., the second frame) sent to the first terminal device by the first network device among the plurality of multilink network devices includes a terminal identifier and / or at least one link identifier. After receiving the terminal identifier and / or at least one link identifier, the first terminal device among the multilink terminal devices stores the identifier locally or in another multilink network device associated with the local area. After completing communication with the multilink network device, the multilink terminal device disconnects through a disassociation and deauthentication process. During the second connection process, the multilink terminal device transmits an identifiable management frame capable of carrying a second link identifier to the multilink network device via the second link, i.e., the link connecting the second network device and the second terminal device. After receiving the management frame via the second link, the multilink network device generates a corresponding management frame response. The multilink terminal device transmits an identifiable management frame capable of carrying a first link identifier to the multilink network device via the first link, i.e., the link connecting the first network device and the first terminal device. After receiving the management frame via the first link, the multilink network device generates a corresponding management frame response. The multilink terminal device transmits an authentication and (re)association frame carrying a terminal identifier to the multilink network device via the first or second link.After receiving an authentication and (re)association frame carrying the terminal identifier, the multilink network device retrieves and responds with the corresponding terminal identifier information via the corresponding link. During the 4-way handshake process, the multilink network device indicates whether it can identify the multilink terminal device by the terminal identifier. Frames sent by the multilink network device to the multilink terminal device include, but are not limited to, the new terminal identifier and / or at least one new link identifier.

[0119] In one embodiment, the first frame is an Access Network Query Protocol (ANQP) request frame. The fourth frame includes information about one or more multilink network devices to which a connection is recommended, and link information corresponding to each multilink network device to which a connection is recommended.

[0120] It should be noted that a multilink terminal device sends an ANQP request frame (ANQP neighbor query) to a multilink network device. The multilink network device can perform access control according to the terminal identifier or link identifier provided by the multilink network device. Specifically, the multilink terminal device sends an ANQP request frame to the multilink network device that includes the terminal identifier and / or at least one link identifier. The multilink network device then identifies the terminal identifier and / or at least one link identifier in the ANQP request frame. Thus, the multilink network device can establish a multilink connection with the multilink terminal device.

[0121] In one embodiment, the first frame is a connection request frame. The fourth frame includes one or more of the following: link indication information indicating links that have been permitted to establish a link; the number of links permitted to establish a link; an indication of whether the requested link is permitted to establish a link; or an indication of whether the requested terminal device is permitted to establish a link.

[0122] In one embodiment, a multilink network device identifies the terminal identifier and / or at least one link identifier of a first frame, i.e., a connection request frame, determines whether those identifiers are the same as existing terminal identifiers and link identifiers, and generates a fourth frame. The fourth frame includes one or more of the following: link indication information indicating links that have been permitted to establish a link; the number of links that have been permitted to establish a link; an indication of whether the requested link is permitted to establish a link; or an indication of whether the requested terminal device is permitted to establish a link.

[0123] Figure 16 shows a flowchart illustrating a method for communication in a multilink network device according to a non-limiting embodiment of this application. The method includes the following operations:

[0124] In operation S210, the multilink network device receives a first frame transmitted by the multilink terminal device. The first frame includes a terminal identifier and / or at least one link identifier.

[0125] In operation S220, the multilink network device identifies the multilink terminal device and the link according to the terminal identifier and / or at least one link identifier.

[0126] In some embodiments, a multilink network device receives a first frame from a multilink terminal device carrying a terminal identifier and / or at least one link identifier. The terminal identifier corresponds to the multilink terminal device, and each of the at least one link identifier corresponds to each of the multiple links. The multilink network device identifies the multilink terminal devices and / or links through the terminal identifier and / or at least one link identifier. This establishes a multilink connection. Corresponding network access services are provided to each multilink terminal device based on the multilink connection. The multilink terminal devices are managed. In addition, the setting of terminal identifiers and link identifiers can reduce sniffing and positioning by third-party devices, improving connection security.

[0127] In one embodiment, a multilink network device identifies a multilink terminal device and / or a link via a terminal identifier and / or at least one link identifier, and feeds back the identification result information to the multilink terminal device. The multilink network device provides feedback to the multilink terminal device when the multilink terminal device and / or the link of the multilink terminal device have been successfully identified by the multilink network device. As a result, the multilink terminal device can send a connection request to the multilink network device to establish a multilink connection between the multilink network device and the multilink terminal device in order to enable simultaneous data transmission over multiple links. The establishment of a multilink connection can enable the network access service corresponding to the multilink terminal device.

[0128] It should be noted that multilink connections enable simultaneous data transmission between multilink network devices and multilink terminal devices via multiple links, thereby improving data transmission throughput, reducing data transmission latency, and thus improving communication efficiency.

[0129] It should be noted that a terminal identifier corresponds to one of several multilink terminal devices. A multilink network device can identify a multilink terminal device based on its terminal identifier. Each of at least one link identifier corresponds to each of several links for connecting to a multilink terminal device. A multilink network device can identify each link based on one of its link identifiers, thereby establishing each link connection with a multilink terminal device.

[0130] In multilink operation technology, it should be noted that MAC addresses can include link-specific MAC addresses and multilink device (MLD) MAC addresses. A multilink terminal device typically has a unique MLD MAC address and at least one link-specific MAC address. The MLD MAC address uniquely identifies the multilink terminal device. Thus, a multilink terminal device corresponds to a link identifier, and a multilink network device can identify a single corresponding multilink terminal device through the link identifier. In addition, while the link-specific MAC addresses of a single multilink terminal device may be different, one of the link-specific MAC addresses of a multilink terminal device may be the same as the MLD MAC address. Therefore, the link identifiers corresponding to multiple links of a single multilink terminal device may be different, and one of the link identifiers may be the same as the terminal identifier. If the frame used for identifying a multilink terminal device carries only the link-specific MAC address, the first frame carries only the link identifier; if the link identifier is the same as the terminal identifier, the first frame carries either the terminal identifier or the link identifier. If the frame used for multilink terminal device identification carries the link-specific MAC address and MLD MAC address of the current link, the first frame carries one terminal identifier and one link identifier. If the frame used for multilink terminal device identification carries the link-specific MAC address of the current link, the link-specific MAC address of another link, and the MLD MAC address, the first frame carries a terminal identifier and multiple link identifiers.

[0131] It should be noted that terminal identifiers and link identifiers may be composed of multilink terminal devices or multilink network devices.

[0132] It should be noted that the first frame is encrypted and transmitted between the multilink terminal device and the multilink network device. Therefore, it is not easy, if not impossible, for a third-party device to sniff and track the terminal identifier and link identifier transmitted by the first frame, thereby improving communication security.

[0133] It should be noted that the first frame is a frame sent by a multilink terminal device to a multilink network device. Typically, the frame is intended to request a connection with the multilink network device. For example, the first frame may be an association request frame in Fast Initial Link Setup (FILS) mode.

[0134] It should be noted that encrypted transmission of the first frame can be achieved via keys. In one embodiment, a multilink terminal device and a multilink network device generate a multilink operation-specific pairwise transient key (PTK) and a link-specific group transient key (GTK) via a four-way handshake on the link, which are used to encrypt and decrypt transmitted unicast and multicast data frames, respectively, to ensure the security of data transmission.

[0135] Referring to Figure 17, according to a non-limiting embodiment, the method further includes the following operations after operation S220.

[0136] In operation S230, the multilink network device transmits a fourth frame to the multilink terminal device. The fourth frame is a response frame to the first frame.

[0137] After receiving the first frame, the multilink network device should note that it identifies the terminal identifier and link identifier to determine whether the same terminal identifier and link identifier are stored locally or in another multilink network device associated with the local area. The multilink network device then generates a fourth frame based on this determination and sends the fourth frame to the multilink 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 on the multilink network device or in a network associated with the local network, the multilink terminal device establishes a multilink connection with the multilink network device and transmits data. Otherwise, the establishment of a connection between the multilink terminal device and the multilink network device fails.

[0138] Referring to Figures 4 and 5, one or both of the first and fourth frames include a first target field. The terminal identifier includes a device identifier. The first target field includes a device identifier information field that includes the terminal identifier and / or at least one link identifier.

[0139] It should be noted that the terminal identifier of a multilink terminal device can be the device ID, which is the device ID of the multilink terminal device. A multilink network device can obtain the ID of a multilink terminal device by identifying the device ID.

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

[0141] In one embodiment, the first frame and the fourth frame each include a first target field schematically shown with reference to Figure 4 or Figure 5. The first target field includes a device identifier information field (device ID information), in which a terminal identifier and / or at least one link identifier are carried. The device identifier information field may carry multiple different device identifiers. The number of bytes (octets) in the device identifier information field is variable, and its specific number can be set according to the number of terminal identifiers and link identifiers.

[0142] Referring to Figures 4 and 5, it can be understood that the first target field further includes a device identifier recognition status field indicating whether the device identifier of the multilink terminal device has been recognized.

[0143] It should be noted that the first target field also includes a Device ID Status field, which indicates whether the device identifier of the multilink terminal device is recognized.

[0144] It should be noted that the device identifier recognition status field is designed to occupy 1 bit. A value of "0" in the device identifier recognition status field indicates an unrecognized device identifier for a multilink terminal device. A value of "1" in the device identifier recognition status field indicates a recognized device identifier for a multilink terminal device.

[0145] It should be noted that the fourth frame received by the multilink terminal device is a response frame to the first frame transmitted by the multilink network device. When the multilink network device recognizes the terminal identifier of the multilink terminal device, the value of the device identifier recognition status field is set to "1". In this case, the multilink network device and the multilink terminal device can establish a connection. If the multilink network device cannot recognize the terminal identifier of the multilink terminal device, the value of the device identifier recognition status field is set to "0". In this case, the establishment of a connection between the multilink network device and the multilink terminal device fails.

[0146] In some embodiments, referring to Figures 4 to 6, the first target field is the following field, namely: A device identifier recognition status tag indicating whether the first target field includes a device identifier recognition status field. A device identifier tag that indicates whether the device identifier information field contains a device identifier. Multiple link tags, each indicating whether the device identifier information field contains the corresponding link identifier, and A device and link identifier sharing indicator tag that indicates whether the device identifier and link identifier have the same value. It further includes a device identifier control bitmap field containing one or more of the following.

[0147] It should be noted that the first target field further includes a device ID control bitmap field compatible with multilink operation technology. Setting the device ID control bitmap field provides the basis for multilink connectivity between multilink terminal devices and multilink network devices.

[0148] It should be noted that the Device ID Status tag indicates whether the first target field contains the Device ID Status field. The Device ID Status tag occupies 1 bit. When the value of the Device ID Status tag is "0", it indicates that the first target field does not contain the Device ID Status field. When the value of the Device ID Status tag is "1", it indicates that the first target field contains the Device ID Status field.

[0149] In one embodiment, a multilink terminal device transmits a first frame to a multilink network device. The first frame includes a terminal identifier and / or at least one link identifier, wherein the terminal identifier in the first frame is pre-configured, and the device identifier in the terminal identifier is the device identifier of the multilink terminal device. In this case, the first target field of the first frame does not include a device identifier recognition field, and therefore the value of the device identifier recognition status tag is set to "0" accordingly.

[0150] It should be noted that the fourth frame is a response frame to the first frame. In one embodiment, after identifying the multilink terminal device according to the terminal identifier in the first frame, the multilink network device generates and transmits the fourth frame to the multilink terminal device. In such a case, the first target field corresponding to the fourth frame includes a device identifier recognition field, and the value of the device identifier recognition status tag is set to "1".

[0151] In one embodiment, referring to Figure 6, the multiple link tags are the first link tag (1st.link ID), the second link tag (2nd.link ID), and the third link tag (3rd.link ID). Each link tag corresponds to a respective link and indicates whether the device identifier recognition information field contains the link identifier for that link. If the value of the link tag is "1", it indicates that the subsequent device identifier information field contains the corresponding link identifier. If the value of the link tag is "0", it indicates that the device identifier information field does not contain the corresponding link identifier.

[0152] It should be noted that the device identifier control bitmap field shown in Figure 6 has three link tags, namely a first link tag, a second link tag, and a third link tag, each link tag occupying 1 bit. In one embodiment, a multilink terminal device and a multilink network device each include three links, namely a first link, a second link, and a third link. The multilink terminal device and the multilink network device can be connected via any one or more of the three links. Each of the first, second, and third links is assigned its own link identifier. In the first frame, when the value of the link tag is "1", it indicates that the multilink terminal device expects to establish a connection with the multilink network device via the corresponding link. For example, if the values ​​of the first and second link tags in the first target field of the first frame are "1" and the value of the third link tag is "0", it indicates that the device identifier information field contains only the link identifiers corresponding to the first and second links, and that the multilink terminal device expects to establish a connection with the multilink device via the first and second links. In the fourth frame, the value of the link tag in the first target field corresponds to the one carried in the first frame. When the value of the recognition status field is "1", it indicates that the device identifier of the multilink terminal device can be identified by the multilink network device.

[0153] It should be noted that if the multilink network device is successfully identified and can identify the device identifier of the multilink terminal device, the value of the recognition status field in the fourth frame will be set to "1". Based on this, the multilink terminal device can send a connection request to the multilink network device so that the multilink terminal device and the multilink network device can establish a connection between the corresponding links and realize a multilink connection.

[0154] The device identifier control bitmap field in Figure 6 is shown as an example only, and it should be noted that it can provide more or fewer link tags. The number of link tags in the device identifier control bitmap field is determined by the number of links between the multilink terminal device and the multilink network device.

[0155] It should be noted that the device identifier control bitmap field includes a device and link identifier sharing indicator tag, which takes 1 bit and indicates whether the device identifier and link identifier share the same value. In multilink operation technology, one of the link-specific MAC addresses of a multilink terminal device may be the same as the MLD MAC address. Therefore, although the link identifiers corresponding to links of the same multilink terminal device are different, one of the link identifiers may be the same as the terminal identifier. If the device identifier and link identifier are the same, the value of the device and link identifier sharing indicator tag is "1", and otherwise it is "0".

[0156] In one embodiment, the device and link identifier sharing indicator is implicit. Specifically, the communication protocol specifies that the terminal identifier and the link identifier are the same. Therefore, it is not necessary to specifically set the device and link identifier sharing indicator in the first target field under the protocol.

[0157] In one embodiment, referring to Figure 6, the device identifier control bitmap field further includes a reserved tag ("Reserved") occupying 2 bits.

[0158] In one embodiment, referring to Figure 7, the device identifier information field includes a length field and a device identifier field.

[0159] It should be noted that the device identifier information field includes a length field and a device ID field. The device identifier field is intended to store the device identifier of the multilink terminal device, and the length field indicates the bit length of the device identifier of the multilink terminal device.

[0160] In one embodiment, referring to Figure 8, the first frame and the fourth frame each include a Media Access Control (MAC) header and a frame body. The first target field is carried in the MAC header or frame body and is a device identifier element field or a device identifier key data encapsulation field.

[0161] It should be noted that the first and fourth frames include a MAC header and a frame body. The first target field is carried in the frame body or MAC header. The first target field is either a device identifier element field or a device identifier key data encapsulation field.

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

[0163] In one embodiment, referring to Figure 4, the device identifier element field includes an element identifier field (Element ID), a length information field (Length), an element identifier extension field (Element ID Extension), a device identifier control bitmap field (Device ID control bitmap), a device identifier recognition status field (Device ID Status), and a device identifier information field (Device ID information). In one embodiment, the element identifier field, length information field, element identifier information extension field, device identifier control bitmap field, and device identifier recognition status field each occupy 1 byte, and the number of bytes in the device identifier information field is set to be variable.

[0164] In one embodiment, referring to Figure 5, during the transmission of the first and fourth frames, the device identifier element field is typically encrypted for transmission to improve the security of the information transmission. After the device identifier element field is encrypted, a device identifier key data encapsulation field is obtained. The device identifier key data encapsulation field includes a device identifier control bitmap field, a device identifier recognition status field, and a device identifier information field (device ID information). In one embodiment, the device identifier control bitmap field and the device identifier recognition status field each occupy one byte, and the number of bytes in the device identifier information field is set to be variable.

[0165] Referring to Figures 6 and 7, it should be noted that the structure and usage of the device identifier control bitmap field, device identifier recognition state field, and device identifier information field within the device identifier element field and device identifier key data encapsulation field are the same, respectively. The device identifier control bitmap field includes a device identifier recognition state tag, a device identifier tag, multiple link tags, a device and link identifier sharing indicator tag, and a reserved tag. Each device identifier information field includes a length field and a device identifier field.

[0166] In one embodiment, referring to Figures 9 and 10, the first frame and / or the fourth frame include a second target field. The terminal identifier includes an identifiable random MAC (IRM) address (IRMA). The second target field includes an IRM field that carries the terminal identifier and / or at least one link identifier.

[0167] It should be noted that the terminal identifier of a multilink terminal device can be set as an IRMA. IRMA is a media access control address randomly assigned to a multilink terminal device. A multilink network device can obtain the media access control address of a multilink terminal device via its IRMA, thereby establishing a connection with the multilink terminal device.

[0168] It should be noted that link identifiers can also be indicated by IRMA. Each link identifier is assigned a corresponding IRMA.

[0169] In one embodiment, the first frame and the fourth frame each include a second target field schematically shown with reference to Figure 9 or Figure 10. The second target field includes an IRM field. Terminal identifiers and / or at least one link identifier are carried in the IRM field. The IRM field may carry multiple different IRMs. The number of bytes (octets) of the IRM field is 6*N, where "6" is the number of bytes in one IRM and "N" is the total number of terminal identifiers and link identifiers carried by the first frame and / or the fourth frame, i.e., the total number of IRMs. The setting of the number of bytes of the IRM field allows the first frame and / or the fourth frame to carry terminal identifiers and / or at least one link identifier.

[0170] In one embodiment, referring to Figures 9 and 10, the second target field further includes an IRM recognition status field indicating whether the IRM of the multilink terminal device is recognized.

[0171] It should be noted that the second target field also includes an IRM recognition status field (Device ID Status) indicating whether the IRM multilink terminal device has been recognized.

[0172] It should be noted that the IRM recognition status field is designed to occupy 1 bit. A value of "0" in the IRM recognition status field indicates an unrecognized IRM for the multilink terminal device. A value of "1" in the device identifier recognition status field indicates a recognized IRM for the multilink terminal device.

[0173] It should be noted that the fourth frame received by the multilink terminal device is a response frame to the first frame transmitted by the multilink network device. When the multilink network device recognizes the IRM of the multilink terminal device, the value of the IRM recognition status field is set to "1". If the multilink network device cannot recognize the IRM of the multilink terminal device, the value of the IRM recognition status field is set to "0".

[0174] In some embodiments, referring to Figures 9 to 11, the second target field is the following field, namely: The second target field includes an IRM recognition status tag indicating whether it contains an IRM recognition status field. IRM tag indicating whether the IRM field contains IRM, and Multiple link tags indicating whether the IRM field carries the corresponding link identifier, and IRM and link identifier sharing indicator tag, which indicates whether the IRM and link identifier share the same value. It further includes an IRM control bitmap field containing one or more of the following.

[0175] It should be noted that the second target field further includes an IRM control bitmap field compatible with multilink operation technology. Setting the IRM control bitmap field provides the basis for multilink connectivity between multilink terminal devices and multilink networks.

[0176] It should be noted that the IRM ID Status tag indicates whether the second target field contains the IRM ID Status field. The IRM ID Status tag occupies 1 bit. If the value of the IRM ID Status tag is "0", it indicates that the second target field does not contain the IRM ID Status field. If the value of the IRM ID Status tag is "1", it indicates that the second target field contains the IRM ID Status field.

[0177] In one embodiment, a multilink terminal device transmits a first frame to a multilink network device. The first frame includes a terminal identifier and / or at least one link identifier, wherein the terminal identifier in the first frame is pre-configured, and the device identifier in the terminal identifier is the device identifier of the multilink terminal device. In this case, the second target field of the first frame does not include an IRM recognition field, and therefore the value of the IRM recognition status tag is correspondingly set to "0".

[0178] It should be noted that the fourth frame is a response frame to the first frame. After identifying the multilink terminal device according to the terminal identifier carried in the first frame, the multilink network device generates the fourth frame and transmits it to the multilink terminal device. In this case, the second target field corresponding to the fourth frame includes an IRM recognition field, and the value of the IRM recognition status tag is "1".

[0179] In one embodiment, referring to Figure 11, the multiple link tags are the first link tag (1st.link ID), the second link tag (2nd.link ID), and the third link tag (3rd.link ID). Each link tag corresponds to a respective link and indicates whether the IRM field contains the link identifier for that link. If the value of a link tag is "1", it indicates that the subsequent IRM field contains the corresponding link identifier. If the value of a link tag is "0", it indicates that the IRM field does not contain the corresponding link identifier.

[0180] It should be noted that the IRM control bitmap field shown in Figure 11 has three link tags, namely a first link tag, a second link tag, and a third link tag, each link tag occupying 1 bit. In one embodiment, a multilink terminal device and a multilink network device each include three links, namely a first link, a second link, and a third link. The multilink terminal device and the multilink network device can be connected via any one or more of the three links. Each of the first, second, and third links is assigned its own link identifier. In the first frame, when the value of the link tag is "1", it indicates that the multilink terminal device expects to establish a connection with the multilink network device via the corresponding link. For example, if the values ​​of the first and second link tags in the second target field of the first frame are "1" and the value of the third link tag is "0", it indicates that the IRM field contains only the link identifiers corresponding to the first and second links, and that the multilink terminal device expects to establish a connection with the multilink device via the first and second links. In the fourth frame, the value of the link tag in the second target field corresponds to the one carried in the first frame. When the value of the recognition status field is "1", it indicates that the IRM of the multilink terminal device can be identified by the multilink network device.

[0181] It should be noted that if the multilink network device is successfully identified and can identify the device identifier of the multilink terminal device, the value of the recognition status field in the fourth frame will be set to "1". Based on this, the multilink terminal device can send a connection request to the multilink network device so that the multilink terminal device and the multilink network device can establish a connection between the corresponding links and realize a multilink connection.

[0182] The IRM control bitmap field in Figure 11 is shown as an example only, and it should be noted that it can provide more or fewer link tags. The number of link tags in the IRM control bitmap field is determined by the number of links between the multilink terminal device and the multilink network device.

[0183] It should be noted that the IRM control bitmap field includes an IRM and link identifier sharing indicator tag, which takes 1 bit and indicates whether the IRM and link identifier share the same value. In multilink operation technology, one of the link-specific MAC addresses of a multilink terminal device may be the same as the MLD MAC address. Therefore, although the link identifiers corresponding to links of the same multilink terminal device are different, one of the link identifiers may be the same as the terminal identifier. If the terminal identifier and IRM corresponding to the link identifier are the same, the value of the IRM and link identifier sharing indicator tag is "1", and otherwise it is "0".

[0184] In one embodiment, the IRM and link identifier sharing indicator are implicit. Specifically, the communication protocol specifies that the terminal identifier and the link identifier are the same. Therefore, it is not necessary to specifically set the IRM and link identifier sharing indicator in the second target field under the protocol.

[0185] In one embodiment, referring to Figure 11, the IRM control bitmap field further includes a reserved tag ("Reserved") occupying 2 bits.

[0186] In one embodiment, referring to Figure 8, the first frame and the fourth frame each include a Media Access Control (MAC) header and a frame body. The second target field is carried in the MAC header or frame body and is an IRM element field or an IRM key data encapsulation field.

[0187] It should be noted that the first and fourth frames include a MAC header and a frame body. The second target field is carried in the frame body. The second target field is an IRM element field or an IRM key data encapsulation field.

[0188] It should be noted that if the terminal identifier and link identifier in the second target field are the same, the terminal identifier is carried in the transmitting-side address (TA) or receiving-side address (RA) field of the MAC header. If the terminal identifier and link identifier are different, the terminal identifier is carried in the frame body, and the link identifier is carried in the TA or RA field of the MAC header.

[0189] In one embodiment, referring to Figure 9, the IRM element field includes an Element ID field, a Length information field, an Element ID Extension field, an IRM control bitmap field, an IRM Status field, and an IRM Information field (IRM Information). In one embodiment, the Element ID field, Length information field, Element ID Extension field, IRM control bitmap field, and IRM Status field each occupy 1 byte. The number of bytes in the IRM field is set to 6*N, where N represents the number of IRMs.

[0190] In one embodiment, referring to Figure 10, during the transmission of the first and fourth frames, the IRM element fields are typically encrypted for transmission to improve the security of the information transmission. After the IRM element fields are encrypted, an IRM key data encapsulation field is obtained. The IRM key data encapsulation field includes an IRM control bitmap field, an IRM status field, and an IRM field (IRM information). In one embodiment, the IRM control bitmap field and the IRM status field each occupy 1 byte, and the number of bytes in the IRM field is set to be variable.

[0191] Referring to Figure 11, it should be noted that the structure and usage of the IRM control bitmap field, IRM recognition state field, and IRM information field within the IRM element field and IRM key data encapsulation field are the same, respectively. The IRM control bitmap field includes the IRM recognition state tag, IRM identifier tag, multiple link tags, IRM and link identifier sharing indicator tag, and reserved tag.

[0192] In one embodiment, a terminal identifier and / or at least one link identifier is generated by the multilink terminal device. Referring to Figure 18, according to a non-limiting embodiment, prior to operation S210, the method further includes the following operations.

[0193] In operation S240, the multilink network device receives the second frame transmitted by the multilink terminal device.

[0194] In operation S250, the multilink network device obtains a terminal identifier and / or at least one link identifier from the second frame.

[0195] It should be noted that before a multilink network device receives a first frame transmitted by a multilink terminal device, the multilink network device receives a second frame transmitted by the multilink terminal device and obtains the terminal identifier and / or at least one link identifier from the second frame. The multilink network device stores the terminal identifier and / or at least one link identifier carried by the second frame locally or on another multilink network device associated with the local device, so that the multilink network device can later identify the terminal identifier and link identifier.

[0196] In one embodiment, the second frame includes at least one of the following: a second authentication frame during a four-way handshake process between a multilink terminal device and a multilink network device; a fourth authentication frame during a four-way handshake process between a multilink terminal device and a multilink network device; a (re)association request frame during a Fast Initial Link Setup (FILS) process between a multilink terminal device and a multilink network device; a first authentication frame during a Pre-Association Security Negotiation (PASN) three-way handshake process between a multilink terminal device and a multilink network device; or a third authentication frame during a PSAN three-way handshake process between a multilink terminal device and a multilink network device.

[0197] It should be noted that the 4-way handshake protocol is intended for unicast key negotiation, and its primary purpose is to ensure that the keys obtained by the applicant and the certifier are the same and up-to-date. The required pairwise transient key (PTK) can be generated by the 4-way handshake, and the process is as follows: The multilink network device sends a first authentication frame to the multilink terminal device during the 4-way handshake. The multilink terminal device sends a second authentication frame to the multilink network device during the 4-way handshake. Upon receiving the second authentication frame during the 4-way handshake, the multilink network device generates a PTK on its end and responds to the multilink terminal device using a third authentication frame during the 4-way handshake. Upon receiving the third authentication frame during the 4-way handshake, the multilink terminal device generates a PTK on its end and responds to the multilink network device using a fourth authentication frame during the 4-way handshake. As a result, the second frame includes the second and fourth authentication frames in the four-way handshake process between the multilink terminal device and the multilink network device.

[0198] In one embodiment, the (re)association request frame of the multilink terminal device and multilink network device during FILS establishment is also a second frame. FILS is primarily intended to accelerate the establishment of connections between multilink terminal devices and multilink network devices. FILS is defined in 802.11ai and allows radio access points, such as multilink network devices, to periodically transmit discovery frames at a shorter 20-millisecond interval compared to the beacon period, enabling multilink terminal devices to discover multilink network devices more quickly. Furthermore, the (re)association in FILS includes Dynamic Host Configuration Protocol (DHCP) information, which allows address configuration to be completed along with the association.

[0199] In one embodiment, the third frame includes a third authentication frame in the PSAN 3-way handshake process between a link terminal device and a multilink network device.

[0200] In one embodiment, referring to Figure 13, during the first connection process, the first terminal device among a plurality of multilink terminal devices discovers a multilink network device that supports multilink operation technology by receiving a beacon and / or probe response frame. The multilink terminal device and the multilink network device complete multilink authentication and connection through a multilink authentication and connection process. During the four-way handshake process, the frame (i.e., the second frame) sent by the first terminal device among the plurality of multilink terminal devices to the first network device includes a terminal identifier and / or at least one link identifier. After receiving the terminal identifier and / or at least one link identifier, the first network device among the multilink network devices stores the identifier locally or in another multilink network device associated with the local area. After completing communication with the multilink network device, the multilink terminal device disconnects through a disassociation and deauthentication process. During the second connection process, the multilink terminal device transmits an identifiable management frame capable of carrying a second link identifier to the multilink network device via the second link, i.e., the link connecting the second network device and the second terminal device. After receiving the management frame via the second link, the multilink network device generates a corresponding management frame response. The multilink terminal device transmits an identifiable management frame capable of carrying a first link identifier to the multilink network device via the first link, i.e., the link connecting the first network device and the first terminal device. After receiving the management frame via the first link, the multilink network device generates a corresponding management frame response. The multilink terminal device transmits an authentication and (re)association frame carrying a terminal identifier to the multilink network device via the first or second link.After receiving an authentication and (re)association frame carrying the terminal identifier, the multilink network device retrieves the corresponding terminal identifier information via the corresponding link and responds. During the 4-way handshake process, the multilink network device indicates whether it can identify the multilink terminal device by the terminal identifier. Frames sent by the multilink terminal device to the multilink network device include, but are not limited to, a new terminal identifier and / or at least one new link identifier.

[0201] In one embodiment, a terminal identifier and / or at least one link identifier is generated by a multilink network device. Referring to Figure 19, according to a non-limiting embodiment, prior to operation S210, the method further includes the following operations.

[0202] In operation S260, the multilink network device transmits a terminal identifier and / or at least one link identifier to the multilink terminal device via a third frame.

[0203] In one embodiment, before receiving a first frame transmitted by a multilink terminal device, the multilink network device transmits a terminal identifier and / or at least one link identifier to the multilink terminal device via a third frame. The terminal identifier and / or at least one link identifier are generated by the multilink network device. Transmitting the third frame allows the multilink network device and the multilink terminal device to have the same terminal identifier and link identifier, thereby facilitating the multilink network device to subsequently identify the terminal identifier and link identifier.

[0204] In one embodiment, the third frame includes at least one of the following: a third authentication frame in a four-way handshake process between a multilink terminal device and a multilink network device; a (re)association response frame in a FILS process between a multilink terminal device and a multilink network device; or a second authentication frame in a PASN three-way handshake process between a multilink terminal device and a multilink network device.

[0205] It should be noted that the 4-way handshake protocol is intended for unicast key negotiation, and its primary purpose is to ensure that the keys obtained by the applicant and the certifier are the same and up-to-date. The required pairwise transient key (PTK) can be generated by the 4-way handshake, and the process is as follows: The multilink network device sends a first authentication frame to the multilink terminal device during the 4-way handshake. The multilink terminal device sends a second authentication frame to the multilink network device during the 4-way handshake. Upon receiving the second authentication frame during the 4-way handshake, the multilink network device generates a PTK on its end and responds to the multilink terminal device using a third authentication frame during the 4-way handshake. Upon receiving the third authentication frame during the 4-way handshake, the multilink terminal device generates a PTK on its end and responds to the multilink network device using a fourth authentication frame during the 4-way handshake. Therefore, the third frame includes a third authentication frame in the four-way handshake process between the multilink terminal device and the multilink network device.

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

[0207] In one embodiment, referring to Figure 15, during the first connection process, the first terminal device among a plurality of multilink terminal devices discovers a multilink network device that supports multilink operation technology by receiving a beacon and / or probe response frame. The multilink terminal device and the multilink network device complete multilink authentication and connection through a multilink authentication and connection process. During the four-way handshake process, a frame (i.e., the second frame) sent to the first terminal device by the first network device among the plurality of multilink network devices includes a terminal identifier and / or at least one link identifier. After receiving the terminal identifier and / or at least one link identifier, the first terminal device among the multilink terminal devices stores the identifier locally or in another multilink network device associated with the local area. After completing communication with the multilink network device, the multilink terminal device disconnects through a disassociation and deauthentication process. During the second connection process, the multilink terminal device transmits an identifiable management frame capable of carrying a second link identifier to the multilink network device via the second link, i.e., the link connecting the second network device and the second terminal device. After receiving the management frame via the second link, the multilink network device generates a corresponding management frame response. The multilink terminal device transmits an identifiable management frame capable of carrying a first link identifier to the multilink network device via the first link, i.e., the link connecting the first network device and the first terminal device. After receiving the management frame via the first link, the multilink network device generates a corresponding management frame response. The multilink terminal device transmits an authentication and (re)association frame carrying a terminal identifier to the multilink network device via the first or second link.After receiving an authentication and (re)association frame carrying the terminal identifier, the multilink network device retrieves and responds with the corresponding terminal identifier information via the corresponding link. During the 4-way handshake process, the multilink network device indicates whether it can identify the multilink terminal device by the terminal identifier. Frames sent by the multilink network device to the multilink terminal device include, but are not limited to, the new terminal identifier and / or at least one new link identifier.

[0208] In one embodiment, the first frame is an Access Network Query Protocol (ANQP) request frame. The fourth frame includes information about one or more multilink network devices to which a connection is recommended, and link information corresponding to each multilink network device to which a connection is recommended.

[0209] It should be noted that a multilink terminal device sends an ANQP request frame (ANQP neighbor query) to a multilink network device. The multilink network device can perform access control according to the terminal identifier or link identifier provided by the multilink network device. Specifically, the multilink terminal device sends an ANQP request frame to the multilink network device that includes the terminal identifier and / or at least one link identifier. The multilink network device then identifies the terminal identifier and / or at least one link identifier in the ANQP request frame. Thus, the multilink network device can establish a multilink connection with the multilink terminal device.

[0210] In one embodiment, the first frame is a connection request frame. The fourth frame includes one or more of the following: link indication information indicating links that have been permitted to establish a link; the number of links permitted to establish a link; an indication of whether the requested link is permitted to establish a link; or an indication of whether the requested terminal device is permitted to establish a link.

[0211] In one embodiment, a multilink network device identifies the terminal identifier and / or at least one link identifier of a first frame, i.e., a connection request frame, determines whether those identifiers are the same as existing terminal identifiers and link identifiers, and generates a fourth frame. The fourth frame includes one or more of the following: link indication information indicating links that have been permitted to establish a link; the number of links that have been permitted to establish a link; an indication of whether the requested link is permitted to establish a link; or an indication of whether the requested terminal device is permitted to establish a link.

[0212] According to one embodiment, an electronic device is provided. As shown in Figure 20, the device includes one or more processors and a memory that stores one or more programs that cause one or more processors to perform a method for communication as described with respect to operations S110-S120 or as described with respect to operations S210-S220 when executed by one or more processors.

[0213] The processor and memory may be connected by a bus or other means.

[0214] As a non-temporary computer-readable storage medium, memory can be configured to store non-temporary software programs and non-temporary computer executable programs. Furthermore, memory may include high-speed random-access memory and non-temporary memory, such as at least one disk memory device, flash memory device, or other non-temporary solid-state memory device. In some embodiments, memory may include memory located remotely from the processor, and these remote memories may be connected to the processor via a network. Examples of networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0215] Non-temporary software programs and instructions for a communication method are stored in memory, when executed by the processor, causing the processor to perform one of the information processing methods in the embodiments described above, for example, operations S110 to S120 described in relation to Figure 2, or operations S210 to S220 described in relation to Figure 16.

[0216] The embodiments of the device described above are illustrative, and the units shown as separate components may or may not be physically separated; that is, they may be located in one place or distributed across several network units. Some or all of the modules may be selected according to the practical needs to achieve the objectives of this embodiment.

[0217] According to one embodiment of the present application, a computer-readable storage medium is provided for storing computer-executable instructions that, when executed by the processor, cause a processor to perform one of the methods described above.

[0218] Those skilled in the art will understand that all or part of the operations and systems disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some or all physical components can be implemented as software executed by a processor such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit such as an application-specific integrated circuit. Such software can be distributed on computer-readable media, which may include computer storage media (or non-temporary media) and communication media (or temporary media). As is well known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and fixed media implemented by any method or technique for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage devices, magnetic boxes, tapes, magnetic disk storage devices or other magnetic storage media, or any other media that can be configured to store desired information and are accessible by a computer. Furthermore, it is well known to those skilled in the art that communication media typically include computer-readable instructions, data structures, program modules, or other data within modulated data signals such as carrier waves or other transmission mechanisms, and can include any information distribution medium.

[0219] Several embodiments of this application will be described in conjunction with the drawings above. However, this disclosure is not limited thereto. Various modifications can be made within the scope of the knowledge of those skilled in the art without departing from the scope of this application. Furthermore, the embodiments and features of the embodiments of this application can be combined with each other without contradiction.

Claims

1. A method for communication, The multilink terminal device obtains a pre-configured terminal identifier and / or at least one link identifier, The multilink terminal device transmits a first frame containing the terminal identifier and / or the at least one link identifier to a multilink network device, causing the multilink network device to identify the multilink terminal device and / or at least one link according to the terminal identifier and / or the at least one link identifier. Methods that include...

2. The method according to claim 1, further comprising the multilink terminal device receiving a fourth frame transmitted by the multilink network device, wherein the fourth frame is a response frame to the first frame.

3. The method according to claim 2, wherein one or both of the first frame and the fourth frame include a first target field, the terminal identifier includes a device identifier, and the first target field includes a device identifier information field that carries the terminal identifier and / or at least one link identifier.

4. The method according to claim 3, wherein the first target field further includes a device identifier recognition status field indicating whether the device identifier of the multilink terminal device is recognized.

5. The first target field further includes a device identifier control bitmap field, and the device identifier control bitmap field is A device identifier recognition status tag indicating whether the first target field includes the device identifier recognition status field, A device identifier tag indicating whether the device identifier information field includes the device identifier, A plurality of link tags, each indicating whether the device identifier information field contains the respective link identifier of the at least one link identifier, and A device and link identifier sharing indicator tag that indicates whether the device identifier and the link identifier share the same value. The method according to claim 4, comprising at least one of the following.

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

7. The method according to claim 3, wherein the first frame and the fourth frame each include a media access control (MAC) header and a frame body, the first target field is carried in the MAC header or the frame body, and the first target field is a device identifier element field or a device identifier key data encapsulation field.

8. The method according to claim 2, wherein one or both of the first frame and the fourth frame include a second target field, the terminal identifier includes an identifiable random MAC (IRM) address (IRMA), and the second target field includes an IRM field that carries the terminal identifier and / or the at least one link identifier.

9. The method according to claim 8, wherein the second target field further includes an IRM recognition status field indicating whether the IRM of the multilink terminal device is recognized.

10. The second target field further includes an IRM control bitmap field, the IRM control bitmap field is An IRM recognition status tag indicating whether the second target field includes the IRM recognition status field, IRM tag indicating whether the IRM field contains the IRM, The IRM field indicates whether each of the link identifiers of the at least one link identifier is carried by a plurality of link tags, or IRM and link identifier sharing indicator tag indicating whether the IRM and link identifier share the same value. The method according to claim 9, comprising at least one of the following.

11. The method according to claim 8, wherein the first frame and the fourth frame each include a media access control (MAC) header and a frame body, the second target field is carried 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.

12. The terminal identifier and / or the at least one link identifier are generated by the multilink terminal device, and the method transmits the first frame to the multilink network device by the multilink terminal device before the method transmits the first frame to the multilink network device. The multilink terminal device transmits the terminal identifier and / or the at least one link identifier to the multilink network device via a second frame. The method according to claim 1, further comprising:

13. The aforementioned second frame is, A second authentication frame during the four-way handshake process between the multilink terminal device and the multilink network device, The fourth authentication frame in the four-way handshake process between the multilink terminal device and the multilink network device, During the establishment of the Fast Initial Link Setup (FILS) process between the multilink terminal device and the multilink network device, the (re)association request frame, The first authentication frame during the pre-association security negotiation (PASN) three-way handshake process between the multilink terminal device and the multilink network device, or The third authentication frame during the PASN three-way handshake process between the multilink terminal device and the multilink network device The method according to claim 12, comprising at least one of the following.

14. The terminal identifier and / or the at least one link identifier are generated by the multilink network device, and before the multilink terminal device obtains the pre-configured terminal identifier and / or the at least one link identifier, the method The multilink terminal device receives a third frame transmitted by the multilink network device, The multilink terminal device obtains the terminal identifier and / or the at least one link identifier from the third frame. The method according to claim 1, further comprising:

15. The third frame described above is A third authentication frame during the four-way handshake process between the multilink terminal device and the multilink network device, The (re)association response frame during the establishment of the Fast Initial Link Setup (FILS) process between the multilink terminal device and the multilink network device, or The second authentication frame during the pre-association security negotiation (PASN) three-way handshake process between the multilink terminal device and the multilink network device. The method according to claim 14, comprising at least one of the following.

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 information about one or more multilink network devices recommended for connection, and link information corresponding to each multilink network device recommended for connection.

17. The first frame described above is a connection request frame, The aforementioned fourth frame is, Link indication information indicating the link for which link establishment has been permitted, The number of links permitted to be established. An indication of whether the link for which a connection has been requested is permitted to establish a link, or an indication of whether the terminal device for which a connection has been requested is permitted to establish a link. The method according to claim 2, comprising one or more of the following.

18. A method for communication, A multilink network device receives a first frame transmitted by a multilink terminal device, wherein the first frame includes a terminal identifier and / or at least one link identifier. The multilink network device identifies the multilink terminal device and the link according to the terminal identifier and / or the at least one link identifier. Methods that include...

19. The method according to claim 18, further comprising the multilink network device transmitting a fourth frame to the multilink terminal device, wherein the fourth frame is a response frame to the first frame.

20. The method according to claim 19, wherein one or both of the first frame and the fourth frame include a first target field, the terminal identifier includes a device identifier, and the first target field includes a device identifier information field that carries the terminal identifier and / or the at least one link identifier.

21. The method according to claim 20, wherein the first target field further includes a device identifier recognition status field indicating whether the device identifier of the multilink terminal device is recognized.

22. The first target field further includes a device identifier control bitmap field, and the device identifier control bitmap field is A device identifier recognition status tag indicating whether the first target field includes the device identifier recognition status field, A device identifier tag indicating whether the device identifier information field includes the device identifier, Multiple link tags, each indicating whether the device identifier information field contains the link identifier of at least one link identifier, or A device and link identifier sharing indicator tag that indicates whether the device identifier and the link identifier share the same value. The method according to claim 21, comprising at least one of the following.

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

24. The method according to claim 20, wherein the first frame and the fourth frame each include a media access control (MAC) header and a frame body, the first target field is carried in the MAC header or the frame body, and the first target field is a device identifier element field or a device identifier key data encapsulation field.

25. The method according to claim 19, wherein one or both of the first frame and the fourth frame include a second target field, the terminal identifier includes an identifiable random MAC (IRM) address (IRMA), and the second target field includes an IRM field that carries the terminal identifier and / or the at least one link identifier.

26. The method according to claim 25, wherein the second target field further includes an IRM recognition status field indicating whether the IRM of the multilink terminal device is recognized.

27. The second target field further includes an IRM control bitmap field, the IRM control bitmap field is An IRM recognition status tag indicating whether the second target field includes the IRM recognition status field, IRM tag indicating whether the IRM field contains the IRM, The IRM field indicates whether each of the link identifiers of the at least one link identifier is carried by a plurality of link tags, or IRM and link identifier sharing indicator tag indicating whether the IRM and link identifier share the same value. The method according to claim 26, comprising at least one of the following.

28. The method according to claim 25, wherein the first frame and the fourth frame each include a media access control (MAC) header and a frame body, the second target field is carried 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.

29. The terminal identifier and / or the at least one link identifier are generated by the multilink terminal device and transmitted by the multilink terminal device before the first frame is received by the multilink network device. The multilink network device receives a second frame transmitted by the multilink terminal device, The multilink network device obtains the terminal identifier and / or the at least one link identifier from the second frame. The method according to claim 18, further comprising:

30. The aforementioned second frame is, A second authentication frame during the four-way handshake process between the multilink terminal device and the multilink network device, The fourth authentication frame in the four-way handshake process between the multilink terminal device and the multilink network device, During the establishment of the Fast Initial Link Setup (FILS) process between the multilink terminal device and the multilink network device, the (re)association request frame, The first authentication frame during the pre-association security negotiation (PASN) three-way handshake process between the multilink terminal device and the multilink network device, or The third authentication frame during the PASN three-way handshake process between the multilink terminal device and the multilink network device The method according to claim 29, comprising at least one of the following.

31. The terminal identifier and / or the at least one link identifier are generated by the multilink network device, and the method is used before the multilink network device receives the first frame transmitted by the multilink terminal device. The multilink network device transmits the terminal identifier and / or the at least one link identifier to the multilink terminal device via a third frame. The method according to claim 18, further comprising:

32. The third frame described above is A third authentication frame during the four-way handshake process between the multilink terminal device and the multilink network device, The (re)association response frame during the establishment of the Fast Initial Link Setup (FILS) process between the multilink terminal device and the multilink network device, or The second authentication frame during the pre-association security negotiation (PASN) three-way handshake process between the multilink terminal device and the multilink network device. The method according to claim 31, comprising at least one of the following.

33. The method according to claim 19, wherein the first frame is an Access Network Query Protocol (ANQP) request frame, and the fourth frame includes information about one or more multilink network devices to which a connection is recommended, and link information corresponding to each multilink network device to which a connection is recommended.

34. The first frame described above is a connection request frame, The aforementioned fourth frame is, Link indication information indicating the link for which link establishment has been permitted, The number of links permitted to be established. An indication of whether the link for which a connection has been requested is permitted to establish a link, or An indication of whether the terminal device requesting the connection is permitted to establish a link. The method according to claim 19, comprising at least one of the following.

35. It is an electronic device, At least one processor, A memory in which at least one program is stored, wherein, when executed by the processor, the memory causes the processor to perform the method according to any one of claims 1 to 17 or any one of claims 18 to 34. An electronic device equipped with the following features.

36. A computer-readable medium storing a computer program, wherein the computer program, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 17 or any one of claims 18 to 34.

Images