Information transmission method, device, and storage medium

Abstract

The present application provides an information transmission method, a device, and a storage medium. The information transmission method applied to a first multi-link device comprises: receiving a specific identifier sent by a first network device; and on the basis of the specific identifier, determining whether the first network device and a third network device belong to a same second network device.

Description

Information transmission method, device and storage medium Technical Field

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

[0002] In the Ultra High Reliability Access Point Multi-Link Device (UHR AP MLD) architecture, each Extremely High Throughput Access Point Multi-Link Device (EHT AP MLD) may have two or three links, and a UHR AP MLD may contain hundreds or even thousands of EHT AP MLDs. A non-AP MLD can establish connections with different links belonging to different EHT AP MLDs under the same UHR AP MLD, such as in a multipoint ranging scenario under the UHR AP MLD architecture. However, a non-AP MLD cannot determine whether two adjacent links and their associated EHT AP MLDs belong to the same UHR AP MLD.

[0003] Summary of the Invention

[0004] In view of this, embodiments of the present application provide an information transmission method, device, and storage medium, which can effectively determine whether the EHT AP MLDs attached to two adjacent links belong to the same UHR AP MLD.

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

[0006] receiving a specific identifier sent by the first network device;

[0007] It is determined based on the specific identifier whether the first network device and the third network device belong to the same second network device.

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

[0009] A specific identifier is sent to the first multi-link device, so that the first multi-link device determines whether the first network device and the third network device belong to the same second network device based on the specific identifier.

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

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

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

[0013] An embodiment of the present application provides a storage medium storing a computer program. When the computer program is executed by a processor, the method described in any one of the above embodiments is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0015] FIG2 is a schematic diagram of an extended format of an RNR field provided by the related art;

[0016] FIG3 is a schematic diagram of a configuration of a multi-link element format provided by the related art;

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

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

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

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

[0021] FIG8 is a schematic diagram of an implementation of an MLO discovery and connection process provided by the related art;

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

[0023] FIG10 is a flowchart of an information transmission method provided in an embodiment of the present application;

[0024] FIG11 is a flowchart of another information transmission method provided in an embodiment of the present application;

[0025] FIG12 is a schematic diagram of an implementation of multi-link discovery, authentication, connection, and four-way handshake provided in an embodiment of the present application;

[0026] FIG13 is a schematic diagram of a configuration of a BSS parameter subfield format in an RNR field provided by a related art;

[0027] FIG14 is a schematic diagram of a configuration of an extended format of a BSS parameter subfield in an RNR field provided by an embodiment of the present application;

[0028] FIG15 is a schematic diagram of a configuration of a TBTT information subfield format in an RNR field provided by a related art;

[0029] FIG16 is a schematic diagram of a configuration of an extended format of a TBTT information subfield in an RNR field provided by an embodiment of the present application;

[0030] FIG17 is a schematic diagram of a configuration of a multi-link element format provided by the related art;

[0031] FIG18 is a schematic diagram of a configuration of a multi-link element format extension provided in an embodiment of the present application;

[0032] FIG19 is a structural block diagram of an information transmission device provided in an embodiment of the present application;

[0033] FIG20 is a structural block diagram of another information transmission device provided in an embodiment of the present application;

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

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

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

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

[0038] Figure 2 is a schematic diagram of an extended format of the RNR field provided by related art. As shown in Figure 2, the Reduced Neighbor Report (RNR) field is expanded to include multi-link device parameter elements (MLD Parameters elements). The MLD Parameters elements include the following fields: AP MLD Identifier (ID), Link ID, Basic Service Set (BSS) Parameter Change Count (All Updates Included), and Disabled Link Indication. The AP MLD ID indicates the relative number of the neighboring AP MLD, and the Link ID indicates the number of each link in the AP MLD.

[0039] Figure 3 is a schematic diagram of a multi-link element format configuration provided by related art. As shown in Figure 3, the frame structure of the Multi-link element format includes the following fields: Multi-link Control, Common Info, and Link Info. The Multi-link Control field indicates whether other related information is carried; the Common Info field indicates multi-link common information; and the Link Info field indicates information about each link.

[0040] The Multi-link element is widely used in the discovery and connection phases. For example, it is carried in the Beacon frame and the Multi-Link Probe Request / Response (ML) frame in the discovery phase, and in the (Re)Association Request / Response (Re)Frame in the connection phase.

[0041] The non-AP MLD uses the MLD ID field to distinguish whether the reported link and the current link belong to the same EHT AP MLD. For example, if MLD ID = 0, it indicates that the reported link and the current link belong to the same EHT AP MLD. When multiple EHT AP MLDs exist around an EHT AP MLD, the current EHT AP MLD uniquely numbers the surrounding EHT AP MLDs to distinguish them.

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

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

[0044] Based on the framework of Figure 4, a complete model of the roaming process is provided, including three stages: pre-roaming, roaming, and post-roaming. Figure 5 is a configuration diagram of a pre-roaming connection model provided by the relevant technology; Figure 6 is a configuration diagram of a roaming connection model provided by the relevant technology; and Figure 7 is a configuration diagram of a post-roaming connection model provided by the relevant technology. As shown in Figure 5, before roaming, a non-AP MLD selects a target AP Group and a target link (link4, link5); as shown in Figure 6, during roaming, the non-AP MLD disconnects a link (AP1) with AP Group 1 and establishes a connection with AP Group 2 (AP4), then repeats the process, disconnecting a link (AP2) with AP Group 1 and establishing a connection with AP Group 2 (AP5), ultimately completing the roaming process, as shown in Figure 7.

[0045] In related technologies, an MLO (Multi-Link Operation) discovery and connection process is provided. During the discovery process, each link of an AP MLD can broadcast a Beacon frame carrying RNR (Reduced Neighbor Report) information. In addition, a non-AP MLD can exchange probe request / response frames with the AP MLD on each link. The non-AP MLD discovers other links belonging to the same AP MLD based on the RNR information carried in the Beacon and probe response frames. It then obtains complete information about each link of the AP MLD by sending an ML probe request and receiving an ML probe response. The non-AP MLD then establishes a connection with the AP MLD through the ML setup process (including MLO association and a 4-way handshake).

[0046] Figure 8 is a schematic diagram of an MLO discovery and connection process implementation provided by the related art. Figure 9 is a network architecture diagram of a UHR AP MLD provided by the related art. In the non-collocated AP MLD (or UHR AP MLD) framework shown in Figure 9, the following issues arise:

[0047] First, each EHT AP MLD may have 2-3 links, while a UHR AP MLD may contain hundreds or even thousands of EHT AP MLDs. However, the Link ID value range is 0-14 or 0-15, which cannot meet the requirements of uniquely identifying each link information in a UHR AP MLD.

[0048] Second, in some scenarios, a non-AP MLD may need to establish connections with different links of different EHT AP MLDs under the same UHR AP MLD, such as in the multi-point ranging scenario under the UHR AP MLD architecture. However, a non-AP MLD cannot determine whether two adjacent links and their attached EHT AP MLDs belong to the same UHR AP MLD.

[0049] Third, during the multi-link association phase, a non-AP MLD can only establish connections with multiple links under one EHT AP MLD and cannot establish connections with multiple links across the EHT AP MLD.

[0050] Fourth, although different EHT AP MLDs can be distinguished by MLD ID, MLD ID can only provide relative information based on the current EHT AP MLD, such as the number of surrounding EHT AP MLDs, and cannot provide unique identification information for each EHT AP MLD in the UHR AP MLD.

[0051] In view of this, an embodiment of the present application provides a discovery and connection solution for multiple EHT AP MLD multi-links of UHR AP MLD under the UHR AP MLD architecture. It should be noted that, for ease of understanding, the relationship between the first network device, the second network device, the third network device and the fourth network device is explained. Among them, the first network device, the third network device and the fourth network device are composed of multiple multi-links and an EHT high MAC, or are an AP MLD device; for example, the first network device, the third network device and the fourth network device can all be EHT AP MLD; the second network device is UHR AP MLD, which can be composed of at least one EHT AP MLD and a UHR high MAC, and the High MAC can be identified by a unique MAC address; the first multi-link device is a non-AP MLD (for example, UHR non-AP MLD). When a new EHT AP MLD accesses the network, the UHR AP MLD assigns a unique first-type device identifier to each newly connected EHT AP MLD.

[0052] The features of the embodiments of the present application may include the following aspects:

[0053] First, the UHR non-AP MLD can use a specific identifier to identify whether different EHT AP MLDs belong to the same UHR AP MLD;

[0054] Second, the UHR AP MLD assigns a unique first-type device identifier (e.g., MLD index or index) to each EHT AP MLD, and the UHR non-AP MLD assigns a unique first-type device identifier (e.g., MLD index or index) to each EHT AP MLD.<index,link ID> You can retrieve information about any link in the UHR AP MLD.

[0055] Third, an EHT AP MLD in a UHR AP MLD can co-host or co-locate a basic service set identifier (BSSID) with an EHT AP MLD that does not belong to the UHR AP MLD.<index,MLD ID,Link ID> Information can be retrieved for any Link that does not belong to this UHR AP MLD.

[0056] Fourthly, during the multi-link connection process, the multi-link (re)association request frame and the multi-link (re)association response frame include multi-link information of multiple EHT AP MLDs, thereby realizing multi-link connection of multiple EHT AP MLDs.

[0057] In one embodiment, Figure 10 is a flowchart of an information transmission method provided by an embodiment of the present application. This embodiment can be used to determine whether two EHT AP MLDs on two adjacent working links belong to the same UHR AP MLD. This embodiment can be executed by a first multi-link device. As shown in Figure 10, this embodiment includes: S110-S120.

[0058] S110: Receive a specific identifier sent by a first network device.

[0059] S120: Determine whether the first network device and the third network device belong to the same second network device based on the specific identifier.

[0060] In an embodiment, the first multi-link device receives a specific identifier sent by the first network device, and determines whether the first network device and the third network device belong to the same second network device based on the specific identifier, thereby enabling the first multi-link device to identify whether the first network device and the third network device belong to the same second network device through a specific identifier.

[0061] In one embodiment, determining whether the first network device and the third network device belong to the same second network device based on the specific identifier includes: determining, based on the specific identifier, whether the first network device to which the current working link of the first multi-link device belongs and the third network device to which at least one link carried by the specific identifier belongs belong to the same second network device.

[0062] In one embodiment, a specific identifier sent by the first network device is received via a beacon frame. During the passive listening process, the first network device sends a specific identifier including at least a second-type device identifier and a first-type device identifier to the first multi-link device via beacon frames on multiple links. The first multi-link device receives the specific identifier sent by the first network device via beacon frames on at least one link, so that the first multi-link device can discover multi-link basic information of one or more second network devices belonging to the same second network device through the specific identifier.

[0063] In one embodiment, the information transmission method applied to the first multi-link device further includes: sending a first probe request frame to the first network device on a working link of the first network device; and receiving a specific identifier sent by the first network device on the working link via a first probe response frame. During active probing, the first multi-link device sends the first probe request frame to at least one first network device of the same second network device on at least one link, and the first network device replies to the first multi-link device on the corresponding link with a first probe response frame, with the first probe response frame carrying a specific identifier including at least a second-type device identifier and a first-type device identifier.

[0064] In one embodiment, the specific identifier includes at least: a second-type device identifier and a first-type device identifier. The second-type device identifier refers to a unique identifier of a UHR AP MLD, for example, the second-type device identifier may be a UHR AP MLD MAC address; the first-type device identifier refers to a unique identifier of an EHT AP MLD, for example, the first-type device identifier may be a multi-link device index (MLD index).

[0065] In one embodiment, the specific identifier is located in the Reduced Neighbor Report RNR field of the beacon frame and the first probe response frame;

[0066] The frame structure of the RNR field includes at least: a same device indication field, used to indicate whether the first network device and the third network device belong to the same second network device; wherein the first network device and the third network device belong to the same type of network device;

[0067] The frame structure of the RNR field includes at least: a first device identifier field, used to indicate the first type of device identifier assigned by the second network device to the third network device. The first network device and the third network device belong to the same type of network device, for example, both are EHT AP MLDs. In beacon frames and first probe response frames sent by the first network device on multiple links, the same device indication field in the RNR field can be used to indicate whether at least one link between the first network device and the third network device belongs to the same second network device, and the first device identifier field in the RNR field can be used to indicate the first type of device identifier corresponding to the third network device corresponding to the link.

[0068] In one embodiment, the beacon frame and the first probe response frame of the specific identifier both include a multilink element field; the frame structure of the state bitmap field in the multilink element field includes at least a first device identifier indication field and a second device identifier indication field, which are respectively used to indicate whether the first type device identifier and the second type device identifier are carried;

[0069] The frame structure of the common information field in the multi-link element field includes at least a first device identifier field and a second device identifier field, which are respectively used to indicate the first type device identifier of the third network device and the second type device identifier of the second network device to which the third network device belongs.

[0070] In one embodiment, the information transmission method applied to the first multi-link device further includes: sending a second probe request frame to the first network device; receiving a specific identifier sent by the first network device through a second probe response frame. The second probe request frame is a multi-link probe request frame; the second probe response frame is a multi-link probe response frame. The second probe request frame and the second probe response frame are used for the multi-link detection process under the same second network device. Under the same second network device, the first multi-link device can send a second probe request frame to at least one first network device under the same second network device on at least one link, and carry the device identifier and link identifier that is expected to be retrieved / requested in the second probe request frame; after the first network device receives the second probe request frame, the first network device replies with a second probe response frame on the corresponding link, and carries the retrieved device identifier and link identifier in the second probe response frame.

[0071] In one embodiment, the specific identifier includes at least: a first-type device identifier, a second-type device identifier, and a link identifier. In this embodiment, the link identifier is used to indicate link information for at least one link under each first network device. The link identifier for each link under each first network device is unique. During multi-link detection on the same second network device, the link identifier may be carried in the second probe request frame and the second probe response frame.

[0072] In one embodiment, the frame structure of the multi-link element field in the second probe request frame includes at least: a first device identifier field corresponding to the third network device desired to be retrieved, a second device identifier field of the second network device to which the third network device belongs, and a link identification field of at least one link in the third network device desired to be retrieved;

[0073] The frame structure of the multi-link element field in the second probe response frame includes at least: the first device identifier field corresponding to the retrieved third network device, the second device identifier field of the second network device to which the third network device belongs, and the link identification field of at least one link in the retrieved third network device.

[0074] In one embodiment, the information transmission method applied to the first multi-link device further includes: sending a third probe request frame to the first network device; receiving a specific identifier sent by the first network device through a third probe response frame. The third probe request frame is a multi-link probe request frame; the third probe response frame is a multi-link probe response frame. The third probe request frame and the third probe response frame are used for the multi-link detection process under different second network devices. Under different second network devices, the first multi-link device can send a third probe request frame on at least one link to a link of at least one first network device under different second network devices, and carry the device identifier and link identifier that is expected to be retrieved / requested in the third probe request frame; after the first network device receives the third probe request frame, the first network device replies with a third probe response frame on the corresponding link, and carries the retrieved device identifier and link identifier in the third probe response frame.

[0075] In one embodiment, the specific identifier includes at least: a first-type device identifier, a second-type device identifier, a link identifier, and a relative identifier of an adjacent first-type device. The relative identifier of an adjacent first-type device is used to indicate the identifier of a first-type device relative to other adjacent first-type devices. The first-type device may be an EHT AP MLD. During multi-link detection for multiple second network devices, the second probe request frame and the second probe response frame may carry the link identifier and the relative identifier of the adjacent first-type device.

[0076] In one embodiment, the frame structure of the multi-link element field in the third probe request frame includes at least: a first device identifier field corresponding to the third network device to be retrieved, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field of the fourth network device, and a link identifier field of at least one link in the fourth network device to be retrieved;

[0077] The frame structure of the multi-link element field in the third probe response frame includes at least: a first device identifier field corresponding to the retrieved third network device, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field, and a link identifier field of at least one link in the retrieved third network device; wherein the fourth network device and the third network device exist on the same physical device.

[0078] In one embodiment, the information transmission method applied to the first multi-link device further includes: sending a multi-link association request frame or a multi-link reassociation request frame to the first network device; and receiving a multi-link association response frame or a multi-link reassociation response frame sent by the first network device. After the first multi-link device and the second network device complete the multi-link authentication process, the first multi-link device can send a multi-link association request frame to the first network device on one link, and the first network device can reply to the first multi-link device on the corresponding link with a multi-link association response frame containing response information of at least one link corresponding to the first multi-link device, and indicating whether each link is allowed to establish a connection; or the first multi-link device can send a multi-link reassociation request frame to the first network device on one link, and the first network device can reply to the first multi-link device on the corresponding link with a multi-link reassociation response frame containing response information of at least one link corresponding to the first multi-link device, and indicating whether each link is allowed to establish a reassociation.

[0079] In one embodiment, the multilink reconnection request frame and the multilink connection request frame each include at least one multilink element field; the frame structure of the at least one multilink element field includes at least: a multilink device identifier field, a first device identifier field, and a link identification field;

[0080] The multilink reconnection response frame and the multilink connection response frame both include a multilink element field; the frame structure of the multilink element field includes at least: a second device identifier field, a first device identifier field, a link identification field, and a link status field;

[0081] Among them, the multi-link device identifier field is used to indicate the identifier of the first multi-link device requested to be connected or reconnected; the second device identifier field is used to indicate the second type device identifier requested to establish a connection or reconnect with the first multi-link device; the first device identifier field is used to indicate the first type device identifier requested to establish a connection or reconnect with the first multi-link device; the link identifier field is used to indicate the link identifier requested to establish a connection or reconnect with the first multi-link device; and the link status field is used to indicate link status information requested to establish a connection or reconnect with the first multi-link device.

[0082] In one embodiment, FIG11 is a flowchart of another information transmission method provided by an embodiment of the present application. This embodiment can be applied to determine whether two EHT AP MLDs on two adjacent working links belong to the same UHR AP MLD. This embodiment can be executed by a first network device. As shown in FIG11 , this embodiment includes: S210.

[0083] S210: Send a specific identifier to the first multi-link device, so that the first multi-link device determines whether the first network device and the third network device belong to the same second network device based on the specific identifier.

[0084] In one embodiment, the information transmission method applied to the first network device further includes:

[0085] A first type device identifier assigned by a second network device is received.

[0086] In one embodiment, the first type device identifier includes at least one of the following: a media access control (MAC) address of the first type device; or a device index of the first type device.

[0087] In one embodiment, the specific identifier is sent to the first multi-link device via a beacon frame.

[0088] In one embodiment, upon receiving the first probe request frame sent by the first multi-link device, the specific identifier is sent to the first multi-link device via a first probe response frame.

[0089] In one embodiment, the specific identifier includes at least: a second type device identifier and a first type device identifier.

[0090] In one embodiment, the specific identifier is located in the Reduced Neighbor Report RNR field of the beacon frame and the first probe response frame;

[0091] The frame structure of the RNR field includes at least: a same device indication field, used to indicate whether the first network device and the third network device belong to the same second network device; wherein the first network device and the third network device belong to the same type of network device;

[0092] The frame structure of the RNR field includes at least: a first device identifier field, used to indicate a first type of device identifier allocated by the second network device to the third network device.

[0093] In one embodiment, the beacon frame and the first probe response frame of the specific identifier both include a multilink element field; the frame structure of the state bitmap field in the multilink element field includes at least a first device identifier indication field and a second device identifier indication field, which are respectively used to indicate whether the first type device identifier and the second type device identifier are carried;

[0094] The frame structure of the common information field in the multi-link element field includes at least a first device identifier field and a second device identifier field, which are respectively used to indicate the first type device identifier of the third network device and the second type device identifier of the second network device to which the third network device belongs.

[0095] In one embodiment, when the second probe request frame sent by the first multi-link device is received, the specific identifier is sent to the first multi-link device via a second probe response frame.

[0096] In one embodiment, the specific identifier includes at least: a first type device identifier, a second type device identifier, and a link identifier.

[0097] In one embodiment, the frame structure of the multi-link element field in the second probe request frame includes at least: a first device identifier field corresponding to the third network device desired to be retrieved, a second device identifier field of the second network device to which the third network device belongs, and a link identification field of at least one link in the third network device desired to be retrieved;

[0098] The frame structure of the multi-link element field in the second probe response frame includes at least: the first device identifier field corresponding to the retrieved third network device, the second device identifier field of the second network device to which the third network device belongs, and the link identification field of at least one link in the retrieved third network device.

[0099] In one embodiment, upon receiving the third probe request frame sent by the first multi-link device, the specific identifier is sent to the first multi-link device via a third probe response frame.

[0100] In one embodiment, the specific identifier includes at least: a first type device identifier, a second type device identifier, a link identifier, and a relative identifier of an adjacent first type device.

[0101] In one embodiment, the frame structure of the multi-link element field in the third probe request frame includes at least: a first device identifier field corresponding to the third network device to be retrieved, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field of the fourth network device, and a link identifier field of at least one link in the fourth network device to be retrieved;

[0102] The frame structure of the multi-link element field in the third probe response frame includes at least: a first device identifier field corresponding to the retrieved third network device, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field, and a link identifier field of at least one link in the retrieved third network device;

[0103] The fourth network device and the third network device are located on the same physical device.

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

[0105] receiving a multi-link association request frame or a multi-link re-association request frame sent by a first multi-link device;

[0106] A multi-link association response frame or a multi-link re-association response frame is sent to the first multi-link device.

[0107] In one embodiment, the multilink reconnection request frame and the multilink connection request frame each include at least one multilink element field; the frame structure of the at least one multilink element field includes at least: a multilink device identifier field, a first device identifier field, and a link identification field;

[0108] The multilink reconnection response frame and the multilink connection response frame both include a multilink element field; the frame structure of the multilink element field includes at least: a second device identifier field, a first device identifier field, a link identification field, and a link status field;

[0109] Among them, the multi-link device identifier field is used to indicate the identifier of the first multi-link device requested to be connected or reconnected; the second device identifier field is used to indicate the second type device identifier requested to establish a connection or reconnect with the first multi-link device; the first device identifier field is used to indicate the first type device identifier requested to establish a connection or reconnect with the first multi-link device; the link identifier field is used to indicate the link identifier requested to establish a connection or reconnect with the first multi-link device; and the link status field is used to indicate link status information requested to establish a connection or reconnect with the first multi-link device.

[0110] It should be noted that for explanations of parameters such as the specific identifier, first type device identifier, second type device identifier, beacon frame, first probe request frame, first probe response frame, second probe request frame, second probe response frame, third probe request frame and third probe response frame involved in the information transmission method applied to the first network device, please refer to the description of the corresponding parameters in the above-mentioned information transmission method applied to the first multi-link device, and will not be repeated here.

[0111] In the following embodiment, Figure 12 is a schematic diagram of an implementation of multi-link discovery, authentication, connection, and a four-way handshake provided by an embodiment of the present application. In this embodiment, the first multi-link device is a non-AP MLD, the first network device is a first EHT AP MLD, the second network device is a UHR AP MLD, the third network device is a second EHT AP MLD; and the fourth network device is a third EHT AP MLD. As shown in Figure 12, the implementation process of multi-link discovery, authentication, connection, and a four-way handshake includes the following steps:

[0112] Step 1: During the passive listening process, the EHT AP MLD notifies the first multi-link device (UHR non-AP MLD) of information such as the UHR AP MLD MAC address and MLD index through management frames such as Beacon and probe response on multiple links. The first multi-link device (UHR non-AP MLD) discovers multiple EHT AP MLDs belonging to the same UHR AP MLD and the basic multi-link information of the EHT AP MLD by receiving the management frames in the above steps on one or more links.

[0113] Step 2, active detection process: The UHR non-AP MLD sends a first probe request frame (referred to as a probe request frame) to one or more EHT AP MLDs of the same UHR AP MLD on one or more links. After receiving the first probe response frame (referred to as a probe request frame) in the above step, the UHR AP MLD replies with a probe response frame on the corresponding link and carries information such as the UHR AP MLD MAC address and MLD index.

[0114] Step 3, multi-link detection process under the same UHR AP MLD: The UHR non-AP MLD sends a second probe request frame (referred to as an ML probe request frame) to at least one EHT AP MLD under the same UHR AP MLD on at least one of the multiple links, carrying the MLD index and link ID information to retrieve one or more link information on a specific EHT AP MLD; after receiving the second probe response frame (referred to as an ML probe request frame) in the above step, the UHR AP MLD replies with an ML probe response frame on the corresponding link and carries the UHR AP MLD information and the requested at least one link information on at least one EHT AP MLD.

[0115] Step 4, multi-link detection process under different UHR AP MLDs: The UHR non-AP MLD sends a third probe request frame (referred to as an ML probe request frame) on at least one link to a link of at least one EHT AP MLD under different UHR AP MLDs, carrying the MLD index, MLD ID, and link ID information to retrieve at least one link information on a specific EHT AP MLD; after receiving the third probe response frame (referred to as an ML probe request frame) in the above step, the UHR AP MLD replies with an ML probe response frame on the corresponding link and carries the UHR AP MLD information and the requested at least one link information on at least one EHT AP MLD.

[0116] In step 5, the UHR non-AP MLD and the UHR AP MLD complete the multi-link authentication process.

[0117] Step 6: The UHR non-AP MLD sends a multi-link association request carrying request information of at least one link of at least one EHT AP MLD to the UHR AP MLD on one link.

[0118] In step 7, the UHR AP MLD replies to the UHR non-AP MLD on the corresponding link with a corresponding multi-link association response including at least one Link response information of at least one EHT AP MLD, and indicates whether each link is allowed to establish a connection.

[0119] The above steps 1-7 are further explained as follows:

[0120] In some application examples, steps 1-4 are discovery processes in different scenarios, and one or more steps may be selected for execution in different application examples.

[0121] In some application examples, in Beacon and probe response frames sent by a first EHT AP MLD on multiple links, the RNR field indicates whether at least one link belonging to a second EHT AP MLD belongs to the same UHR AP MLD, as well as the MLD index of the second EHT AP MLD corresponding to the link. Figure 13 illustrates a configuration diagram of the BSS parameter subfield format in the RNR field, as provided in the related art. Table 1 describes the field name and explanation of each field in the RNR field.

[0122] Table 1 Explanation of the RNR field

[0123] Figure 14 is a schematic diagram of an extended format configuration of the BSS parameter subfield in the RNR field according to an embodiment of the present application. As shown in Figure 14, based on the RNR field shown in Figure 13, a Same UHR AP MLD field is added to indicate whether the reported AP / Link and the current AP / Link belong to the same UHR AP MLD.

[0124] Figure 15 is a schematic diagram of the configuration of the target beacon transmission time (TBTT) information subfield format in the RNR field provided by the related art. The format of the TBTT information field in the RNR field is shown in Figure 15, and the explanation of each field is shown in Table 1.

[0125] Figure 16 is a schematic diagram of a configuration of an expanded format of the TBTT information subfield in the RNR field provided by an embodiment of the present application. As shown in Figure 16, based on the TBTT information field shown in Figure 15, an MLD index field is added to the TBTT field to indicate the index value assigned by the UHR AP MLD to uniquely identify an EHT AP MLD, which may also be referred to as a first type device identifier.

[0126] In some application examples, the Beacon,probe response frame sent by the first EHT AP MLD indicates the UHR AP MLD MAC address information and its assigned MLD index information through the multi-link elements field, as shown in Figure 18. Figure 17 is a configuration diagram of a multi-link element format provided by the related art. The format configuration of the multi-link element is shown in Figure 17, and the explanation of each field is shown in Table 2.

[0127] Table 2 Schematic diagram of the explanation of the fields in the multilink element format

[0128] Figure 18 is a schematic diagram of a multilink element format extension configuration provided by an embodiment of the present application. As shown in Figure 18, based on the configuration shown in Figure 17, the MLD index present and UHR AP MLD MAC present fields are added to the Present bitmap field to indicate whether the MLD index information and UHR AP MLD MAC address are carried, respectively.

[0129] The MLD index field is added to the Common Info field to indicate the index value assigned by the UHR AP MLD to the EHT AP MLD corresponding to the Link; the UHR MAC address field is added to indicate the MAC address information of the UHR AP MLD corresponding to the Link.

[0130] In some application examples, during the implementation of step 3, in the ML probe request frame sent by the first non-AP MLD to the first EHT AP MLD, the frame structure of the multi-link elements field includes at least a first device identifier field corresponding to the third network device to be retrieved, a second device identifier field of the second network device to which the third network device belongs, and a link identifier field of at least one link in the third network device to be retrieved. The first device identifier field corresponding to the third network device to be retrieved is used to indicate MLD index information assigned by at least one second EHT AP MLD; the second device identifier field of the second network device to which the third network device belongs is used to indicate a second type of device identifier (e.g., UHR AP MLD MAC address information) of the UHR AP MLD to which the second EHT AP MLD belongs; and the link identifier field of at least one link in the third network device to be retrieved is used to indicate link ID information corresponding to at least one link in the second EHT AP MLD to be retrieved.

[0131] In some application examples, during the implementation of step 3, in the ML probe response frame replied by the first EHT AP MLD, the frame structure of the multi-link elements field includes at least: a first device identifier field corresponding to the retrieved third network device, a second device identifier field of the second network device to which the third network device belongs, and a link identifier field of at least one link retrieved in the third network device; wherein the second device identifier field of the second network device to which the third network device belongs is used to indicate UHR AP MLD MAC address information; the first device identifier field corresponding to the retrieved third network device is used to indicate the MLD index assigned by the requested at least one second EHT AP MLD; and the link identifier field of at least one link in the retrieved third network device is used to indicate all or part of the link information of the requested at least one second EHT AP MLD.

[0132] In some application examples, the second EHT AP MLD and a third EHT AP MLD that does not belong to the same UHR AP MLD coexist on the same physical device. During the implementation of step 4, when the first non-AP MLD retrieves specific link information of the third EHT AP MLD through the first EHT AP MLD, the first non-AP MLD sends an ML probe request frame to the first EHT AP MLD. The multi-link elements field in the ML probe request frame includes: a first device identifier field corresponding to the third network device to be retrieved, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field of the fourth network device, and a link identifier field of at least one link in the fourth network device to be retrieved. The second device identifier field of the second network device to which the third network device belongs is used to indicate UHR AP MLD MAC address information; the first device identifier field corresponding to the third network device to be retrieved is used to indicate an MLD index assigned by the second EHT AP MLD; the relative identifier field of the fourth network device is used to indicate MLD ID information of the third EHT AP MLD indicated by the second EHT AP MLD; and the link identifier field of at least one link in the fourth network device to be retrieved is used to indicate link ID information of at least one link in the third EHT AP MLD indicated by the second EHT AP MLD.

[0133] In some application examples, during the implementation of step 4, the first EHT AP MLD sends an ML probe response frame, where the multi-link elements field in the ML probe response frame includes: a retrieved first device identifier field corresponding to the third network device, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field, and a retrieved link identifier field of at least one link in the third network device; wherein the second device identifier field of the second network device to which the third network device belongs is used to indicate UHR AP MLD MAC address information; the retrieved first device identifier field corresponding to the third network device is used to indicate an MLD index assigned by the second EHT AP MLD; the relative identifier field is used to indicate MLD ID information of the third EHT AP MLD indicated by the second EHT AP MLD; and the retrieved link identifier field of at least one link in the third network device is used to indicate all or part of the information of at least one link in the requested second EHT AP MLD.

[0134] In some application examples, in a multi-link (re)association request ((re)association request) frame sent by a non-AP MLD to a first EHT AP MLD, the multi-link (re)association request frame includes at least one multi-link element (multi-link element) field. The frame structure of each multi-link element field includes at least: a multi-link device identifier field, a first device identifier field, and a link identifier field. The multi-link device identifier field is used to indicate an identifier of the first multi-link device for which connection or reconnection is requested, such as the non-AP MLD MAC address; the first device identifier field is used to indicate an identifier of a first type of device for which connection or reconnection is requested with the first multi-link device, such as an MLD index (or MLD ID); and the link identifier field is used to indicate an identifier of a link for which connection or reconnection is requested with the first multi-link device, such as at least one Link ID information, as shown in FIG18 .

[0135] In some application examples, in a multi-link (re)association response ((re)association response) frame sent by the EHT AP MLD to the first non-AP MLD, the multi-link (re)association response frame includes at least one multi-link element (multi-link element) field. The frame structure of each multi-link element field includes at least: a second device identifier field, a first device identifier field, a link identifier field, and a link status field. The second device identifier field is used to indicate a second type of device identifier for requesting to establish a connection or reconnect with the first multi-link device, such as the UHR AP MLD MAC address; the first device identifier field is used to indicate a first type of device identifier for requesting to establish a connection or reconnect with the first multi-link device, such as the MLD index (or MLD ID); the link identifier field is used to indicate a link identifier for requesting to establish a connection or reconnect with the first multi-link device, such as at least one Link ID information; and the link status field is used to indicate link status information for requesting to establish a connection or reconnect with the first multi-link device, such as Link status information, as shown in FIG18 .

[0136] In one embodiment, FIG19 is a block diagram of an information transmission apparatus provided in an embodiment of the present application. This embodiment is applied to a first multi-link device. As shown in FIG19 , the information transmission apparatus in this embodiment includes: a receiver 410 and a determination module 420.

[0137] The receiver 410 is configured to receive the specific identifier sent by the first network device.

[0138] The determination module 420 is configured to determine whether the first network device and the third network device belong to the same second network device based on the specific identifier.

[0139] In one embodiment, determining whether the first network device and the third network device belong to the same second network device based on the specific identifier includes: determining, based on the specific identifier, whether the first network device to which the current working link of the first multi-link device belongs and the third network device to which at least one link carried by the specific identifier belongs belong to the same second network device.

[0140] In one embodiment, the specific identifier sent by the first network device is received via a beacon frame.

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

[0142] a transmitter configured to send a first probe request frame to the first network device over a working link of the first network device;

[0143] The receiver is further configured to receive a specific identifier sent by the first network device on a working link through a first probe response frame.

[0144] In one embodiment, the specific identifier includes at least: a second type device identifier and a first type device identifier.

[0145] In one embodiment, the specific identifier is located in the Reduced Neighbor Report RNR field of the beacon frame and the first probe response frame;

[0146] The frame structure of the RNR field includes at least: a same device indication field, used to indicate whether the first network device and the third network device belong to the same second network device; wherein the first network device and the third network device belong to the same type of network device;

[0147] The frame structure of the RNR field includes at least: a first device identifier field, used to indicate a first type of device identifier allocated by the second network device to the third network device.

[0148] In one embodiment, the beacon frame and the first probe response frame of the specific identifier both include a multilink element field; the frame structure of the state bitmap field in the multilink element field includes at least a first device identifier indication field and a second device identifier indication field, which are respectively used to indicate whether the first type device identifier and the second type device identifier are carried;

[0149] The frame structure of the common information field in the multi-link element field includes at least a first device identifier field and a second device identifier field, which are respectively used to indicate the first type device identifier of the third network device and the second type device identifier of the second network device to which the third network device belongs.

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

[0151] The transmitter is further configured to send a second probe request frame to the first network device;

[0152] The receiver is further configured to receive the specific identifier sent by the first network device through a second probe response frame.

[0153] In one embodiment, the specific identifier includes at least: a first type device identifier, a second type device identifier, and a link identifier.

[0154] In one embodiment, the frame structure of the multi-link element field in the second probe request frame includes at least: a first device identifier field corresponding to the third network device desired to be retrieved, a second device identifier field of the second network device to which the third network device belongs, and a link identification field of at least one link in the third network device desired to be retrieved;

[0155] The frame structure of the multi-link element field in the second probe response frame includes at least: the first device identifier field corresponding to the retrieved third network device, the second device identifier field of the second network device to which the third network device belongs, and the link identification field of at least one link in the retrieved third network device.

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

[0157] The transmitter is further configured to send a third probe request frame to the first network device;

[0158] The receiver is further configured to receive the specific identifier sent by the first network device through a third probe response frame.

[0159] In one embodiment, the specific identifier includes at least: a first type device identifier, a second type device identifier, a link identifier, and a relative identifier of an adjacent first type device.

[0160] In one embodiment, the frame structure of the multi-link element field in the third probe request frame includes at least: a first device identifier field corresponding to the third network device to be retrieved, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field of the fourth network device, and a link identifier field of at least one link in the fourth network device to be retrieved;

[0161] The frame structure of the multi-link element field in the third probe response frame includes at least: a first device identifier field corresponding to the retrieved third network device, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field, and a link identifier field of at least one link in the retrieved third network device;

[0162] The fourth network device and the third network device are located on the same physical device.

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

[0164] The transmitter is further configured to send a multi-link association request frame or a multi-link re-association request frame to the first network device;

[0165] The receiver is further configured to receive a multi-link association response frame or a multi-link re-association response frame sent by the first network device.

[0166] In one embodiment, the multilink reconnection request frame and the multilink connection request frame each include at least one multilink element field; the frame structure of the at least one multilink element field includes at least: a multilink device identifier field, a first device identifier field, and a link identification field;

[0167] The multilink reconnection response frame and the multilink connection response frame both include a multilink element field; the frame structure of the multilink element field includes at least: a second device identifier field, a first device identifier field, a link identification field, and a link status field;

[0168] Among them, the multi-link device identifier field is used to indicate the identifier of the first multi-link device requested to be connected or reconnected; the second device identifier field is used to indicate the second type device identifier requested to establish a connection or reconnect with the first multi-link device; the first device identifier field is used to indicate the first type device identifier requested to establish a connection or reconnect with the first multi-link device; the link identifier field is used to indicate the link identifier requested to establish a connection or reconnect with the first multi-link device; and the link status field is used to indicate link status information requested to establish a connection or reconnect with the first multi-link device.

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

[0170] In one embodiment, FIG20 is a block diagram of another information transmission device provided in an embodiment of the present application. This embodiment is applied to a first network device. As shown in FIG20 , the information transmission device in this embodiment includes: a transmitter 510.

[0171] The transmitter 510 is configured to send a specific identifier to the first multi-link device, so that the first multi-link device determines whether the first network device and the third network device belong to the same second network device based on the specific identifier.

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

[0173] The receiver is configured to receive a first-type device identifier allocated by the second network device.

[0174] In one embodiment, the first type device identifier includes at least one of the following: a media access control (MAC) address of the first type device; or a device index of the first type device.

[0175] In one embodiment, the specific identifier is sent to the first multi-link device via a beacon frame.

[0176] In one embodiment, upon receiving the first probe request frame sent by the first multi-link device, the specific identifier is sent to the first multi-link device via a first probe response frame.

[0177] In one embodiment, the specific identifier includes at least: a second type device identifier and a first type device identifier.

[0178] In one embodiment, the specific identifier is located in the Reduced Neighbor Report RNR field of the beacon frame and the first probe response frame;

[0179] The frame structure of the RNR field includes at least: a same device indication field, used to indicate whether the first network device and the third network device belong to the same second network device; wherein the first network device and the third network device belong to the same type of network device;

[0180] The frame structure of the RNR field includes at least: a first device identifier field, used to indicate a first type of device identifier allocated by the second network device to the third network device.

[0181] In one embodiment, the beacon frame and the first probe response frame of the specific identifier both include a multilink element field; the frame structure of the state bitmap field in the multilink element field includes at least a first device identifier indication field and a second device identifier indication field, which are respectively used to indicate whether the first type device identifier and the second type device identifier are carried;

[0182] The frame structure of the common information field in the multi-link element field includes at least a first device identifier field and a second device identifier field, which are respectively used to indicate the first type device identifier of the third network device and the second type device identifier of the second network device to which the third network device belongs.

[0183] In one embodiment, when the second probe request frame sent by the first multi-link device is received, the specific identifier is sent to the first multi-link device via a second probe response frame.

[0184] In one embodiment, the specific identifier includes at least: a first type device identifier, a second type device identifier, and a link identifier.

[0185] In one embodiment, the frame structure of the multi-link element field in the second probe request frame includes at least: a first device identifier field corresponding to the third network device desired to be retrieved, a second device identifier field of the second network device to which the third network device belongs, and a link identification field of at least one link in the third network device desired to be retrieved;

[0186] The frame structure of the multi-link element field in the second probe response frame includes at least: the first device identifier field corresponding to the retrieved third network device, the second device identifier field of the second network device to which the third network device belongs, and the link identification field of at least one link in the retrieved third network device.

[0187] In one embodiment, upon receiving the third probe request frame sent by the first multi-link device, the specific identifier is sent to the first multi-link device via a third probe response frame.

[0188] In one embodiment, the specific identifier includes at least: a first type device identifier, a second type device identifier, a link identifier, and a relative identifier of an adjacent first type device.

[0189] In one embodiment, the frame structure of the multi-link element field in the third probe request frame includes at least: a first device identifier field corresponding to the third network device to be retrieved, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field of the fourth network device, and a link identifier field of at least one link in the fourth network device to be retrieved;

[0190] The frame structure of the multi-link element field in the third probe response frame includes at least: a first device identifier field corresponding to the retrieved third network device, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field, and a link identifier field of at least one link in the retrieved third network device;

[0191] The fourth network device and the third network device are located on the same physical device.

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

[0193] The receiver is further configured to receive a multi-link association request frame or a multi-link re-association request frame sent by the first multi-link device;

[0194] The transmitter is further configured to send a multi-link association response frame or a multi-link re-association response frame to the first multi-link device.

[0195] In one embodiment, the multilink reconnection request frame and the multilink connection request frame each include at least one multilink element field; the frame structure of the at least one multilink element field includes at least: a multilink device identifier field, a first device identifier field, and a link identification field;

[0196] The multilink reconnection response frame and the multilink connection response frame both include a multilink element field; the frame structure of the multilink element field includes at least: a second device identifier field, a first device identifier field, a link identification field, and a link status field;

[0197] Among them, the multi-link device identifier field is used to indicate the identifier of the first multi-link device requested to be connected or reconnected; the second device identifier field is used to indicate the second type device identifier requested to establish a connection or reconnect with the first multi-link device; the first device identifier field is used to indicate the first type device identifier requested to establish a connection or reconnect with the first multi-link device; the link identifier field is used to indicate the link identifier requested to establish a connection or reconnect with the first multi-link device; and the link status field is used to indicate link status information requested to establish a connection or reconnect with the first multi-link device.

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

[0199] In one embodiment, Figure 21 is a schematic diagram of the structure of a communication device provided by an embodiment of the present application. As shown in Figure 21, the device provided by the present application includes: a processor 610, a memory 620, and a communication interface 630. The number of processors 610 in the device can be one or more, and Figure 21 uses one processor 610 as an example. The number of memories 620 in the device can be one or more, and Figure 21 uses one memory 620 as an example. The processor 610, memory 620, and communication interface 630 of the device can be connected via a bus or other means, and Figure 21 uses a bus connection as an example. In this embodiment, the device can be a first multi-link device or a first network device.

[0200] The memory 620, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the device of any embodiment of the present application (e.g., the receiver 410 and determination module 420 in the information transmission device of the first multi-link device). The memory 620 may include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function; the data storage area may store data generated based on the use of the device. Furthermore, the memory 620 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some embodiments, the memory 620 may further include memory remotely located relative to the processor 610, and such remote memory may be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. The communication interface 630 is used for communication between multiple communication devices.

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

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

[0203] An embodiment of the present application further provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform an information transmission method applied to a first multi-link device. The method includes: receiving a specific identifier sent by a first network device; and determining, based on the specific identifier, whether the first network device and a third network device belong to the same second network device.

[0204] An embodiment of the present application further provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform an information transmission method applied to a first network device. The method includes: sending a specific identifier to a first multi-link device, so that the first multi-link device determines whether the first network device and a third network device belong to the same second network device based on the specific identifier.

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

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

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

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

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

Claims

1. An information transmission method, applied to a first multi-link device, comprising: receiving a specific identifier sent by a first network device; It is determined whether the first network device and the third network device belong to the same second network device based on the specific identifier.

2. The method according to claim 1, wherein: The determining, based on the specific identifier, whether the first network device and the third network device belong to the same second network device includes: Based on the specific identifier, it is determined whether the first network device to which the current working link of the first multi-link device belongs and the third network device to which at least one link carried by the specific identifier belongs belong to the same second network device.

3. The method according to claim 1, wherein: The specific identifier sent by the first network device is received through a beacon frame.

4. The method according to claim 1, further comprising: Sending a first probe request frame to the first network device on a working link of the first network device; The specific identifier sent by the first network device on the one working link is received through a first probe response frame.

5. The method according to claim 3 or 4, wherein: The specific identifier includes at least: a second type device identifier and a first type device identifier.

6. The method according to claim 3 or 4, wherein: The specific identifier is located in the reduced neighbor report RNR field of the beacon frame and the first probe response frame; The frame structure of the RNR field includes at least: a same device indication field, used to indicate whether the first network device and the third network device belong to the same second network device; wherein the first network device and the third network device belong to the same type of network device; The frame structure of the RNR field includes at least: a first device identifier field, used to indicate a first type of device identifier allocated by the second network device to the third network device.

7. The method according to claim 3 or 4, wherein: The beacon frame of the specific identifier and the first detection response frame both include a multilink element field; the frame structure of the state bitmap field in the multilink element field includes at least a first device identifier indication field and a second device identifier indication field, which are used to indicate whether a first type device identifier and a second type device identifier are carried, respectively; The frame structure of the public information field in the multilink element field at least includes a first device identifier field and a second device identifier field, which are respectively used to indicate the first type device identifier of the third network device. identifier, and a second type device identifier of the second network device to which the third network device belongs.

8. The method according to claim 1, further comprising: Sending a second probe request frame to the first network device; The specific identifier sent by the first network device is received through a second probe response frame.

9. The method according to claim 8, wherein: The specific identifier includes at least: a first type device identifier, a second type device identifier and a link identifier.

10. The method according to claim 8, wherein: The frame structure of the multi-link element field in the second probe request frame includes at least: a first device identifier field corresponding to the third network device to be retrieved, a second device identifier field of the second network device to which the third network device belongs, and a link identification field of at least one link in the third network device to be retrieved; The frame structure of the multi-link element field in the second detection response frame includes at least: the first device identifier field corresponding to the retrieved third network device, the second device identifier field of the second network device to which the third network device belongs, and the link identification field of at least one link in the retrieved third network device.

11. The method according to claim 1, further comprising: Sending a third probe request frame to the first network device; The specific identifier sent by the first network device is received through a third probe response frame.

12. The method according to claim 11, wherein: The specific identifier includes at least: a first type device identifier, a second type device identifier, a link identifier, and a relative identifier of an adjacent first type device.

13. The method according to claim 11, wherein: The frame structure of the multi-link element field in the third probe request frame includes at least: a first device identifier field corresponding to the third network device to be retrieved, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field of the fourth network device, and a link identifier field of at least one link in the fourth network device to be retrieved; The frame structure of the multi-link element field in the third detection response frame includes at least: a first device identifier field corresponding to the retrieved third network device, a second device identifier field of the second network device to which the third network device belongs, a relative identifier field, and a link identifier field of at least one link in the retrieved third network device; The fourth network device and the third network device exist on the same physical device.

14. The method according to claim 1, further comprising: Sending a multilink association request frame or a multilink reassociation request frame to the first network device; Receive a multi-link association response frame or a multi-link re-association response frame sent by the first network device.

15. The method according to claim 14, wherein: The multilink reconnection request frame and the multilink connection request frame each include at least one multilink element field; The frame structure of the at least one multilink element field includes at least: a multilink device identifier field, a first device identifier field and a link identification field; The multilink reconnection response frame and the multilink connection response frame both include a multilink element field; the frame structure of the multilink element field includes at least: a second device identifier field, a first device identifier field, a link identification field, and a link status field; Among them, the multi-link device identifier field is used to indicate the identifier of the first multi-link device requested to be connected or reconnected; the second device identifier field is used to indicate the second type of device identifier requested to establish a connection or reconnect with the first multi-link device; the first device identifier field is used to indicate the first type of device identifier requested to establish a connection or reconnect with the first multi-link device; the link identification field is used to indicate the link identification requested to establish a connection or reconnect with the first multi-link device; the link status field is used to indicate the link status information of the request to establish a connection or reconnect with the first multi-link device.

16. An information transmission method, applied to a first network device, comprising: A specific identifier is sent to the first multi-link device, so that the first multi-link device determines whether the first network device and the third network device belong to the same second network device based on the specific identifier.

17. The method according to claim 16, further comprising: A first type device identifier assigned by a second network device is received.

18. The method according to claim 17, wherein: The first type device identifier includes at least one of the following: a media access control MAC address of the first type device; and a device index of the first type device.

19. The method according to claim 16, wherein: The specific identifier is sent to the first multi-link device through a beacon frame.

20. The method according to claim 16, wherein: In case of receiving the first probe request frame sent by the first multi-link device, the specific identifier is sent to the first multi-link device through a first probe response frame.

21. The method according to claim 16, wherein: In case of receiving the second probe request frame sent by the first multi-link device, the specific identifier is sent to the first multi-link device through a second probe response frame.

22. The method according to claim 16, wherein: In case of receiving the third probe request frame sent by the first multi-link device, the specific identifier is sent to the first multi-link device through a third probe response frame.

23. The method according to any one of claims 16 to 22, further comprising: receiving a multilink association request frame or a multilink reassociation request frame sent by the first multilink device; Sending a multi-link association response frame or a multi-link re-association response frame to the first multi-link device.

24. A communication device comprising: memory, and at least one processor; The memory is configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the method as described in any one of claims 1 to 15 or 16 to 23.

25. A storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 15 or 16 to 23.

Images