Information allocation method, device, and storage medium

Abstract

The present application provides an information distribution method, a device, and a storage medium. The information allocation method applied to a first network device comprises: when a first network device accesses a network system where a second network device is located, receiving a unique multi-link device identifier allocated by the second network device; and when the first network device is disconnected from the network system where the second network device is located, triggering the second network device to recover the multi-link device identifier.

Description

Information distribution method, device and storage medium Technical Field

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

[0002] Within the framework of two types of non-collocated AP MLDs (also known as ultra-high reliability AP MLDs), each UHR AP MLD can assign a network-wide unique association identifier (AID) to each UHR non-AP MLD. Furthermore, a UHR AP MLD may contain multiple extremely high-throughput access point multi-link device (EHT AP MLD) physical nodes. In large-scale enterprise and public networks, the number of EHT AP MLD nodes can range from hundreds to tens of thousands, and each EHT AP MLD can simultaneously provide services to dozens of non-AP MLDs. Using the traditional 16-bit AID to indicate each UHR non-AP MLD can easily lead to AID indication conflicts.

[0003] Summary of the Invention

[0004] In view of this, embodiments of the present application provide an information distribution method, device, and storage medium, which solve the problem of AID indication conflict caused by insufficient AID resources.

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

[0006] When a first network device accesses a network system where a second network device is located, receiving a unique multi-link device identifier assigned by the second network device;

[0007] When the first network device goes offline from the network system where the second network device is located, the second network device is triggered to reclaim the multi-link device identifier.

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

[0009] When a first network device accesses a network system where a second network device is located, allocating a unique multi-link device identifier to the first network device;

[0010] When the first network device goes offline from the network system where the second network device is located, the multi-link device identifier corresponding to the first network device is recovered.

[0011] The present invention provides an information distribution method, which is applied to a terminal device and includes:

[0012] When a terminal device establishes an initial connection with a second network device via a first network device, a first identifier assigned by the first network device is received.

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

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

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

[0016] 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

[0017] FIG1 is a schematic diagram of a format configuration of an AID field provided by the related art;

[0018] FIG2 is a schematic diagram of a format configuration of a TIM field provided by the related art;

[0019] FIG3 is a schematic diagram of an implementation of a multi-link connection establishment process provided by the related art;

[0020] FIG4 is a configuration diagram of a UHR AP MLD architecture of a centralized UHR upper MAC provided in the related art;

[0021] FIG5 is a configuration diagram of a distributed UHR AP MLD architecture provided by the related art;

[0022] FIG6 is a flow chart of an information distribution method provided in an embodiment of the present application;

[0023] FIG7 is a flowchart of another information distribution method provided in an embodiment of the present application;

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

[0025] FIG9 is a schematic diagram of a flow chart of allocation and recovery of a multi-link device identifier and a first identifier according to an embodiment of the present application;

[0026] FIG10 is a schematic diagram of a format configuration of a UHR AID information element provided in an embodiment of the present application;

[0027] FIG11 is a schematic diagram of a configuration of a multi-link (re)connection request / response frame provided in an embodiment of the present application;

[0028] FIG12 is a schematic diagram of a configuration of a state bitmap subfield in a multi-link reconfiguration message provided by a related art;

[0029] 13 is a schematic diagram of the configuration of a common information field in a multi-link reconfiguration message provided by the related art;

[0030] 14 is a schematic diagram of an extended configuration of a status bitmap subfield in a multi-link reconfiguration message provided in an embodiment of the present application;

[0031] 15 is a schematic diagram of an extended configuration of a common information field in a multi-link reconfiguration message according to an embodiment of the present application;

[0032] FIG16 is a schematic diagram of a UHR non-AP MLD roaming scenario under a distributed UHR upper MAC architecture according to an embodiment of the present application;

[0033] FIG17 is a schematic diagram illustrating an implementation of UHR AID allocation and recovery under a centralized UHR upper MAC architecture according to an embodiment of the present application;

[0034] FIG18 is a structural block diagram of an information distribution device provided in an embodiment of the present application;

[0035] FIG19 is a structural block diagram of another information distribution device provided in an embodiment of the present application;

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

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

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

[0039] In a Basic Service Set (BSS) network, the AID field contains a 16-bit value assigned by the access point (AP) during the connection process. This value uniquely identifies a connected station (STA). In a Mesh Basic Service Set (MBSS) network, an AID is assigned by one mesh station (Mesh STA) to another mesh STA. Figure 1 shows a format configuration of an AID field, as provided in related art. As shown in Figure 1, each AID occupies 2 bytes.

[0040] In a basic BSS network, the value range of the AID field is 1-2007, occupying 14 bits, with the highest two bits set to 11.

[0041] In IoT below 1 GHz, the value range of the AID field is 1-8191, with the top three digits reserved.

[0042] AIDs are widely used in functions such as channel status (sounding) collection, trigger frame allocation of channel resources, and unicast buffer indication. Taking the trigger frame and unicast buffer indication functions as examples, they are described as follows:

[0043] (1) Trigger frame: After a STA connects to an AP, the AP uses a 12-bit AID (AID12) to identify each STA. In the trigger frame, the AP uses AID12 to identify the resource unit (RU) allocated to each STA.

[0044] (2) Unicast Buffer Indication: In the beacon frame sent by the AP containing the Traffic Indication Message (TIM) field, the AP uses AID information to indicate the buffer status of each STA. Figure 2 is a schematic diagram of a TIM field format configuration provided by the related art. As shown in Figure 2 , the Element ID field is used to fill in the identifier of the TIM field; the Length field indicates the length of the field; the DTIM Counter field indicates the number of Beacon frames before the Delivery Traffic Indication Message (DTIM) appears in this field. A DTIM Count of 0 indicates that the TIM is a DTIM; any other value indicates that the field is a TIM; the DTIM Period field indicates the frequency of occurrence of the field (an integer multiple of the Beacon Period); the Bitmap Control field contains AID control information; and the Partial Virtual Bitmap field has a length of 0 to 251 bytes. Each bit in the Partial Virtual Bitmap field indicates whether there is unicast data cache information for the corresponding STA. A bit of 1 indicates cache information, while a bit of 0 indicates no cache. The maximum number of STAs that can be cached is 2007.

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

[0046] 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 3 is a schematic diagram of a multi-link connection establishment process provided by related art. As shown in Figure 3, 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).

[0047] The Wi-Fi 8 protocol introduces UHR AP MLD, which allows the deployment of subordinate APs within the same UHR AP MLD in different locations to address latency issues associated with device roaming. Furthermore, the collaboration of multiple subordinate APs within the same UHR AP MLD can help address channel utilization issues.

[0048] A centralized UHR AP MLD architecture is provided in the seamless roaming solution under the non-parallel AP MLD architecture. 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. 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) and a UHR upper MAC deployed on different physical device nodes. UHR non-AP MLD can establish a link connection with the low media access control (Low MAC) of any node without switching the connected network, thereby solving the data transmission delay problem caused by network switching.

[0049] Another distributed UHR AP MLD architecture is proposed in the Seamless Roaming for UHR solution. Figure 5 is a configuration diagram of a distributed UHR AP MLD architecture provided by the related art. As shown in Figure 5, based on the original two EHT AP MLDs deployed on different physical device nodes, a controller for multi-AP MLD control is added. Each EHT AP MLD can share the context information of the non-AP MLD with each other, and each UHR non-AP MLD can only establish a connection with one EHT AP MLD. When the UHR non-AP MLD switches from one EHT AP MLD (EHT AP MLD 1) to another EHT AP MLD (EHT AP MLD X), the context information of the UHR non-AP MLD is also switched from EHT AP MLD 1 to EHT AP MLD X.

[0050] The embodiments of the present application provide an information allocation method under two UHR AP MLD architectures (i.e., a centralized UHR upper MAC UHR AP MLD architecture and a distributed UHR AP MLD architecture). UHR AIDs can be allocated to each UHR non-AP MLD through the UHR AP MLD, solving the problem of AID conflict indication caused by insufficient AID resources in the related art. At the same time, the information allocation method proposed in the present application is compatible with traditional single-link STAs and EHT non-AP MLDs, and is compatible with the current function of using AIDs to uniquely identify STAs in the sounding process, Trigger frames, and TIM fields.

[0051] For ease of understanding, the first network device provided in the embodiment of the present application may be an EHT AP MLD; the second network device may be a UHR AP MLD; and the terminal device may be a UHR non-AP MLD or an EHT non-AP MLD.

[0052] In one embodiment, FIG6 is a flowchart of an information allocation method provided in an embodiment of the present application. This embodiment is applied to automatically allocating a first identifier to a non-AP MLD in a UHR AP MLD architecture. This embodiment can be executed by a first network device. As shown in FIG6 , this embodiment includes: S110-S120.

[0053] S110 : When a first network device accesses a network system where a second network device is located, receive a unique multi-link device identifier assigned by the second network device.

[0054] S120: When the first network device goes offline from the network system where the second network device is located, trigger the second network device to reclaim the multi-link device identifier.

[0055] In one example, the network system where the second network device resides can be a UHR AP MLD distributed network system or a UHR AP MLD centralized network system. The second network device maintains the allocation and recovery of the first network device. After a new first network device accesses the network system where the second network device resides, the second network device allocates a network-wide unique multi-link device identifier to the newly accessed first network device. After a first network device goes offline from the network system where the second network device resides, the second network device recovers the multi-link device identifier it allocated to the offline first network device.

[0056] In one embodiment, when a terminal device establishes a first connection with a second network device through a first network device, the first network device assigns a first identifier to the terminal device. When a terminal device establishes a first connection with a second network device through a first network device, the first network device assigns a first identifier to the terminal device. When a terminal device establishes a first connection with a second network device through at least two first network devices, at least two first network devices belonging to the same second network device collaborate to assign a first identifier to the terminal device. The first identifier includes a multi-link device identifier and a connection identifier. When a terminal device establishes a first connection with a second network device through at least one first network device, a first network device or at least two first network devices negotiate to assign a first identifier to the terminal device, which may include: updating the multi-link device identifier, or updating the connection identifier, or updating both the multi-link device identifier and the connection identifier, to ensure that each first network device uniquely identifies each terminal device using the first identifier.

[0057] In one embodiment, when a terminal device roams between at least two first network devices, the at least two first network devices collaborate to reallocate a first identifier for the terminal device and reclaim the previously allocated first identifier. When a terminal device roams between at least two first network devices, the at least two first network devices negotiate to reallocate a first identifier for the terminal device and reclaim the previously allocated first identifier. The first identifier includes a multi-link device identifier and a connection identifier. The first identifier reallocated to the terminal device through negotiation between the at least two first network devices may include: updating the multi-link device identifier, or updating the connection identifier, or updating both the multi-link device identifier and the connection identifier, thereby ensuring that each first network device uniquely identifies each terminal device using the first identifier.

[0058] In one embodiment, when a terminal device performs a partial link handover between at least two first network devices, the first identifier allocated to the terminal device remains unchanged. In one example, when a terminal device switches a partial link from one first network device to another first network device, the first identifier allocated to the terminal device by the first network device may remain unchanged. In another example, when a terminal device switches a full link from a first first network device to another first network device, the multi-link device identifier in the first identifier allocated to the terminal device by the first network device is updated, but the connection identifier may remain unchanged. In this case, there is no need to notify the terminal device of the change in its multi-link device identifier through signaling.

[0059] In one embodiment, when a terminal device roams on multiple links of the same first network device, the first identifier allocated to the terminal device by the first network device remains unchanged. Each first network device may include multiple links. When a terminal device switches from multiple links of the first network device to another multiple links of the first network device, the first identifier allocated to the terminal device by the first network device may remain unchanged.

[0060] In one embodiment, when a terminal device is disconnected from a second network device, the first network device reclaims the first identifier of the terminal device. In another example, when a terminal device establishes a connection with a second network device through multiple first network devices, and when the terminal device is disconnected from the second network device, the multiple first network devices belonging to the same second network device reclaim the allocated first identifier. In another example, when a terminal device establishes a connection with a second network device through a first network device, and when the terminal device is disconnected from the second network device, the first network device reclaims the first identifier allocated to the terminal device.

[0061] In one embodiment, the connection identifier in the first identifier assigned by the first network device to the terminal device is the same across multiple links. When a terminal device establishes a connection with a second network device via at least one first network device, multiple first network devices on the relevant links negotiate to assign a first identifier to the terminal device, and the connection identifier on each link of the terminal device is the same.

[0062] In one embodiment, the first network device as the target device obtains the context information of the terminal device in the first network device as the source device using the first identifier. In the case where the terminal device switches all links from the first network device as the source device to the first network device as the target device, the terminal device and the first network device as the target device exchange update information of the first identifier using a connection request frame / connection response frame, or a reconnection request frame / reconnection response frame. For example, the terminal device sends a connection or reconnection request frame to the first network device as the target device, and then on the return link, the first network device as the target device obtains the context information of the terminal device from the first network device as the source device using the first identifier, and applies it to the first network device as the target device. The first network device as the target device sends a connection / reconnection response frame to the terminal device, and includes the latest assigned first identifier in the connection / reconnection response frame.

[0063] In one embodiment, the context information includes at least one of the following: a frame sequence number (SN); a frame number (PN packet number); target wake-up time (TWT) negotiation information; block acknowledgement (BA) negotiation information, block acknowledgement scoreboard (Block ACK soreboarding) information, and PTK information.

[0064] In one embodiment, when at least two first network devices assign a first identifier to a terminal device, if the at least two first network devices do not have the same connection identifier, establishment of some links between the terminal device and the second network device fails. When a terminal device simultaneously establishes connections with different links of at least two first network devices belonging to the same second network device, or switches at least one link to a first network device, at least two first network devices belonging to the same second network device negotiate to reallocate a first identifier to the terminal device. If the at least two first network devices cannot negotiate a common unassigned connection identifier via a backhaul link, establishment of some links between the terminal device and the second network device fails.

[0065] In one embodiment, the first identifier includes a multi-link device identifier and a connection identifier. The first identifier assigned by the first network device to the terminal device includes both the multi-link device identifier and the connection identifier. The multi-link device identifier is a network-wide unique device identifier assigned by the second network device to each first network device. In one embodiment, the multi-link device identifier includes one of the following: a Media Access Control (MAC) address of the first network device; or a first network device identifier. The first network device identifier may be an index value of the first network device.

[0066] In one embodiment, the information carried by the first identifier includes one of the following: a connection response frame; a connection request frame; a reconnection request frame; a reconnection response frame; a multilink reconfiguration request message; a multilink reconfiguration response message, or a BSS Transition Management (BTM) request / response frame. The connection response frame and the connection request frame form a pair; the reconnection request frame and the reconnection response frame form a pair; and the multilink reconfiguration request message and the multilink reconfiguration response message form a pair.

[0067] In one embodiment, the frame body of a connection request frame, a connection response frame, a reconnection request frame, and a reconnection response frame includes a first identifier field for indicating a first identifier assigned by the first network device to the terminal device. The first identifier field can be configured in the connection request frame, the connection response frame, the reconnection request frame, and the reconnection response frame. The first identifier field includes a multilink device identifier field and a connection identifier field. The multilink device identifier field indicates a multilink device identifier assigned by the second network device to the first network device; the connection identifier field indicates a connection identifier assigned by the first network device to the terminal device. In a connection request frame or a reconnection request frame, the multi-link device identification field is used to indicate the multi-link device identification of the first network device to which the terminal device is connected before roaming, and the connection identifier field is used to indicate a connection identifier assigned by a first network device to which the terminal device is connected before roaming, or a connection identifier assigned by negotiation between at least two first network devices; in a connection response frame or a reconnection response frame, the multi-link device identification field is used to indicate the multi-link device identification of the first network device to which the terminal device is connected after roaming, and the connection identifier field is used to indicate a connection identifier reallocated by a first network device to which the terminal device is connected after roaming, or a connection identifier reallocated by negotiation between at least two first network devices.

[0068] In one embodiment, the status bitmap field in the multi-link reconfiguration request message and the multi-link reconfiguration response message includes at least a connection identifier indication field, which is used to indicate whether the first identifier assigned by the first network device to the terminal device is carried; the common information field in the multi-link reconfiguration message and the multi-link reconfiguration response message includes at least a first identifier field, which is used to indicate the first identifier assigned by the first network device to the terminal device. When the connection identifier indication field is 1, it is used to indicate that the first identifier assigned by the first network device to the terminal device can be carried; when the connection identifier indication field is 0, it is used to indicate that the first identifier assigned by the first network device to the terminal device cannot be carried. In one example, the connection identifier indication field can occupy 1 bit; the first identifier field can occupy 4 or 6 bytes, and the first identifier field includes a multi-link device identification field and a connection identifier field, the multi-link device identification field occupies 2 or 4 bytes, and the connection identifier field occupies 2 bytes.

[0069] In one embodiment, the reconnection request frame and the multilink reconfiguration request message both carry the first identifier allocated by the first network device to the terminal device;

[0070] Both the reconnection response frame and the multi-link reconfiguration response message carry the first identifier reallocated by the first network device to the terminal device. In the multi-link reconfiguration request message, the multi-link device identification field is used to indicate the multi-link device identification of the first network device to which the terminal device was connected before roaming, and the connection identifier field is used to indicate a connection identifier allocated by a first network device to which the terminal device was connected before roaming, or a connection identifier allocated by negotiation between at least two first network devices. In the multi-link reconfiguration response message, the multi-link device identification field is used to indicate the multi-link device identification of the first network device to which the terminal device is connected after roaming, and the connection identifier field is used to indicate a connection identifier reallocated by a first network device to which the terminal device is connected after roaming, or a connection identifier reallocated by negotiation between at least two first network devices.

[0071] In one embodiment, FIG7 is a flowchart of another information allocation method provided by an embodiment of the present application. This embodiment is applied to automatically assigning a first identifier to a non-AP MLD in a UHR AP MLD architecture. This embodiment can be executed by a second network device. As shown in FIG7 , this embodiment includes: S210-S220.

[0072] S210 : When a first network device accesses a network system where a second network device is located, a unique multi-link device identifier is allocated to the first network device.

[0073] S220: When the first network device goes offline from the network system where the second network device is located, reclaim the multi-link device identifier corresponding to the first network device.

[0074] In one example, after a new first network device joins the network system where a second network device resides, the second network device assigns a network-wide unique multi-link device identifier to the newly joined first network device. After a first network device goes offline from the network system where the second network device resides, the second network device reclaims the multi-link device identifier it assigned to the offline first network device.

[0075] It should be noted that, for explanations of parameters such as the multi-link device identifier in the information distribution method applied to the second network device, refer to the description of corresponding parameters in the above-mentioned information distribution method applied to the first network device, which will not be repeated here.

[0076] In one embodiment, FIG8 is a flowchart of another information allocation method provided by an embodiment of the present application. This embodiment is applied to the case of automatically allocating a first identifier to a non-AP MLD in a UHR AP MLD architecture. This embodiment can be executed by a terminal device. As shown in FIG8 , this embodiment includes: S310.

[0077] S310: When a terminal device establishes an initial connection with a second network device through a first network device, receive a first identifier assigned by the first network device.

[0078] In one embodiment, when roaming occurs between at least two first network devices, the terminal device receives a first identifier reallocated by the at least two first network devices in a collaborative manner.

[0079] In one embodiment, when the terminal device performs a partial link handover between at least two first network devices, the first identifier allocated to the terminal device by the at least two first network devices remains unchanged.

[0080] In one embodiment, when the terminal device roams on multiple links of the same first network device, the first identifier allocated to the terminal device by the first network device remains unchanged.

[0081] In one embodiment, when the terminal device is disconnected from the second network device, the first network device reclaims the first identifier of the terminal device.

[0082] In one embodiment, the connection identifier in the first identifier allocated by the first network device to the terminal device is the same on multiple links. In one embodiment, when roaming occurs between at least two first network devices, the information allocation method applied to the terminal device further includes:

[0083] Sending the allocated first identifier to the first network device as the target device, so that the first network device as the target device obtains the context information of the terminal device from the first network device as the source device using the allocated first identifier;

[0084] A first identifier reallocated by a first network device serving as a target device is received.

[0085] In an embodiment, the terminal device sends a first identifier to a first network device serving as a target device; the first network device serving as a target device then uses the first identifier to obtain context information from the first network device serving as a source device; and the first network device serving as a target device then reallocates the first identifier to the terminal device.

[0086] In one embodiment, the context information includes at least one of the following: a frame sequence number; a frame number; target wake-up time negotiation information; block acknowledgement negotiation information, block acknowledgement scoreboard information, and PTK information.

[0087] In one embodiment, when at least two first network devices allocate a first identifier to a terminal device, if the at least two first network devices do not have the same connection identifier, establishment of a partial link between the terminal device and the second network device fails.

[0088] In one embodiment, the first identifier includes a multi-link device identifier and a connection identifier.

[0089] In one embodiment, the multi-link device identification includes one of the following: a MAC address of the first network device; or an identifier of the first network device.

[0090] In one embodiment, the information carried by the first identifier includes one of the following: a connection response frame; a connection request frame; a reconnection request frame; a reconnection response frame; a multilink reconfiguration request message; or a multilink reconfiguration response message.

[0091] In one embodiment, the frame bodies of the connection request frame, the connection response frame, the reconnection request frame, and the reconnection response frame include a first identifier field for indicating a first identifier allocated by the first network device to the terminal device.

[0092] In one embodiment, the state bitmap field in the multi-link reconfiguration request message and the multi-link reconfiguration response message includes at least a connection identifier indication field, which is used to indicate whether the first identifier allocated by the first network device to the terminal device is carried;

[0093] The common information field in the multi-link reconfiguration request message and the multi-link reconfiguration response message includes at least a first identifier field, which is used to indicate a first identifier allocated by the first network device to the terminal device.

[0094] In one embodiment, the reconnection request frame and the multilink reconfiguration request message both carry the first identifier allocated by the first network device to the terminal device;

[0095] Both the reconnection response frame and the multi-link reconfiguration response message carry the first identifier reallocated by the first network device to the terminal device.

[0096] In an embodiment, a connection request frame can be used in a scenario where a terminal device establishes an initial connection with a second network device through a first network device. The terminal device sends a connection request frame to the first network device. After the first network device receives the connection request frame, the first network device sends a connection response frame to the terminal device and assigns a new first identifier to the terminal device through the connection response frame.

[0097] It should be noted that the explanation of parameters such as the first identifier, multi-link device identifier and connection identifier in the information allocation method applied to the terminal device, as well as the allocation and recovery process of the first identifier and the explanation of the allocation and recovery process of the multi-link identifier, can be found in the corresponding description in the above-mentioned information allocation method applied to the first network device, and will not be repeated here.

[0098] In the following embodiment, the allocation and recovery process is described by taking the first network device as an EHT AP MLD, the second network device as a UHR AP MLD, the terminal device as a UHR non-AP MLD, the multi-link device identifier as an EHT AP MLD ID (referred to as MLD ID for short), the connection identifier as an AID, and the first identifier as an EHT AP MLD ID+AID (referred to as UHR AID for short) as an example.

[0099] In one example, FIG9 is a flow chart of the allocation and recovery of a multi-link device identifier and a first identifier provided by an embodiment of the present application. As shown in FIG9 , the allocation and recovery process of the multi-link device identifier and the first identifier in this embodiment includes:

[0100] S410 : The UHR AP MLD allocates a unique MLD ID to each EHT AP MLD that joins the network.

[0101] After a new EHT AP MLD node is connected to the UHR AP MLD distributed network system, the UHR AP MLD allocates a network-wide unique EHT AP MLD ID (MLD ID for short) to each EHT AP MLD.

[0102] S420: At least one EHT AP MLD allocates a UHR AID to the connected UHR non-AP MLD.

[0103] When a UHR non-AP MLD establishes a connection with a UHR AP MLD through an EHT AP MLD node, an EHT AP MLD on the relevant link allocates the first UHR AID to the UHR non-AP MLD; when a UHR non-AP MLD establishes a connection with a UHR AP MLD through multiple EHT AP MLD nodes, multiple EHT AP MLDs on the relevant links collaborate to allocate the first UHR AID to the UHR non-AP MLD, and the AID field on each link of the UHR non-AP MLD (that is, the AID included in the UHR AID) is the same.

[0104] S430: When the UHR non-AP MLD roams between at least two links of an EHT AP MLD or between at least two EHT AP MLDs, at least one EHT AP MLD reallocates a UHR AID to the UHR non-AP MLD.

[0105] When a UHR non-AP MLD roams between at least two links of an EHT AP MLD, an EHT AP MLD configures a second UHR AID for the UHR non-AP MLD and reclaims the first UHR AID. When a UHR non-AP MLD roams between at least two links of an EHT AP MLD, the first UHR AID allocated by the EHT AP MLD may not be updated, that is, the first UHR AID is not reclaimed. When a UHR non-AP MLD roams between multiple EHT AP MLDs, the multiple EHT AP MLDs configure a second UHR AID for the UHR non-AP MLD through negotiation and reclaim the first UHR AID. The update of the UHR AID includes the update of the EHT AP MLD ID in the UHR AID, or the update of the AID in the suffix, or the update of both the EHT AP MLD ID and the AID, in order to ensure that each EHT AP MLD can uniquely identify each UHR non-AP MLD using the UHR AID information.

[0106] S440: When the UHR non-AP MLD is disconnected from the UHR AP MLD, at least one EHT AP MLD reclaims the UHR AID most recently allocated by the UHR non-AP MLD.

[0107] When the UHR non-AP MLD is disconnected from the UHR AP MLD, if the UHR non-AP MLD establishes a connection with the UH AP MLD through an EHT AP MLD, the EHT AP MLD reclaims the UHR AID of the UHR non-AP MLD; if the UHR non-AP MLD establishes connections with the UH AP MLD through multiple EHT AP MLDs, the multiple EHT AP MLDs collaborate to reclaim the UHR AID of the UHR non-AP MLD.

[0108] S450: After an EHT AP MLD goes offline from the UHR AP MLD, the UHR AP MLD reclaims the MLD ID allocated to it.

[0109] After an EHT AP MLD node goes offline from the UHR AP MLD, the UHR AP MLD reclaims the MLD ID allocated by it.

[0110] The above steps S410-S450 are further described as follows:

[0111] In some application examples, the UHR AP MLD allocates and reclaims the MLD ID for each EHT AP MLD through the backhaul network.

[0112] In some application examples, the MLD ID may be an EHT AP MLD MAC address or an EHT AP MLD index value.

[0113] In some application examples, when a UHR non-AP MLD switches part of its link from one EHT AP MLD to another EHT AP MLD, its UHR AID information may remain unchanged.

[0114] In some application instances, when a UHR non-AP MLD switches all links from one EHT AP MLD to another EHT AP MLD, the EHT AP MLD ID information in the UHR AID is updated, but the AID information may remain unchanged. In this case, it may not be necessary to notify the UHR non-AP MLD of the change in its EHT MLD ID through signaling.

[0115] In some application examples, when a UHR non-AP MLD simultaneously establishes connections with different links of multiple EHT AP MLDs belonging to the UHR AP MLD, or at least one link is switched to an EHT AP MLD, these EHT AP MLDs negotiate a common unassigned AID through the backhaul network (for example, when the UHR non-AP MLD establishes three links with EHT AP MLD1, EHT AP MLD2, and EHT AP MLD3, AID = 100 is the unassigned AID of EHT AP MLD1, EHT AP MLD2, and EHT AP MLD3), and send the AID to the UHR non-AP MLD through a (re)association response frame.

[0116] In some application examples, when a UHR non-AP MLD simultaneously establishes connections with different links of multiple EHT AP MLDs belonging to the UHR AP MLD or switches at least one link to one EHT AP MLD, these EHT AP MLDs cannot negotiate a common unassigned AID through the backhaul network, resulting in some link establishment failures (for example, when the UHR non-AP MLD sends a (re)association request frame on the link belonging to the first EHT AP MLD to establish three links with the first EHT AP MLD, the second EHT AP MLD, and the third EHT AP MLD, AID=100 is an AID that is unassigned by the first and second EHT AP MLDs, but AID=100 has been assigned to another terminal device in the third EHT AP MLD). The first UHR AP MLD sends the AID to the UHR non-AP MLD via a (re)association response frame, and the (re)association response frame carries a connection rejection message for the link located in the third EHT AP MLD.

[0117] In some application examples, when the UHR non-AP MLD switches all links from the first EHT AP MLD to the second EHT AP MLD, the UHR non-AP MLD and the second EHT AP MLD use (Re)association request / response to exchange updated information of the UHR AID. For example, the UHR non-AP MLD sends the (Re)association request frame shown in Figure 3-4 to the second EHT AP MLD. On the backhaul link, the second EHT AP MLD uses the UHR AID to obtain the context information of the UHR non-AP MLD from the first EHT AP MLD, such as the frame sequence number (SN), frame number (PN packet number), target wake-up time (TWT) negotiation, block acknowledgement (BA) negotiation, PTK, etc., and applies it to the second EHT AP MLD. The second EHT AP MLD sends a (Re)association response frame containing the newly allocated UHR AID to the UHR non-AP MLD.

[0118] In some application instances, when the UHR AID information of the UHR non-AP MLD changes, an EHT AP MLD reconfigures a second UHR AID, or multiple EHT AP MLDs negotiate a second UHR AID and inform the UHR non-AP MLD through a management frame, and reclaim the first UHR AID.

[0119] In some application examples, a controller or UHR AP MLD uniquely identifies information of each UHR non-AP MLD through UHR AID information.

[0120] In some application examples, the UHR non-AP MLD is uniquely identified by the EHT AP MLD ID and the assigned AID information carried by the EHT AP MLD.

[0121] In one example, FIG10 is a schematic diagram of a format configuration of a UHR AID information element provided by an embodiment of the present application. The format of the UHR AID information element in this example is shown in FIG10 , and the meaning of each field is explained in Table 1.

[0122] Table 1 UHR AID element field meaning

[0123] Figure 11 is a schematic diagram of the configuration of a multilink (re)association request / response frame provided in an embodiment of the present application. As shown in Figure 11, the (re)association request / response frame carries parameters in the UHR AID element format shown in Figure 10.

[0124] Figure 12 is a schematic diagram of the configuration of the status bitmap subfield in a multi-link reconfiguration message provided by the related art. Figure 13 is a schematic diagram of the configuration of the common information field in a multi-link reconfiguration message provided by the related art. As shown in Figure 12, the status bitmap subfield (Present Bitmap subfield) provided in the multi-link reconfiguration action (ML reconfiguration action) frame is used to indicate whether the ML reconfiguration message carries the MLD MAC address, the Enhanced multi-link (EML) capability set, the MLD capability set, and other information. As shown in Figure 13, the common information field (Common Info field) contains the specific content of the MLD MAC address, the EML capability set, the MLD capability set, and other information (if carried).

[0125] Figure 14 is a schematic diagram of an extended configuration of a status bitmap subfield in a multi-link reconfiguration message provided in an embodiment of the present application. Figure 15 is a schematic diagram of an extended configuration of a common information field in a multi-link reconfiguration message provided in an embodiment of the present application. For a multi-link reconfiguration (ML Reconfiguration) message, the extended formats of the status bitmap subfield (Presence Bitmap subfield) and the common information field (Common Info field) in the ML Reconfiguration are shown in Figures 14 and 15, respectively. That is, a connection identifier indication field (UHR AID present) is added to the Present Bitmap subfield, and a first identifier field (UHR AID field) with a length of 4 or 6 bytes is added to the Common Info field, and a multi-link device identification field (MLD ID field) and a connection identifier field (AID field) are included in the UHR AID field. In one embodiment, the multi-link reconfiguration message includes a multi-link reconfiguration request message and a multi-link reconfiguration response message.

[0126] In an example, for two different scenarios, a distributed UHR upper MAC and a centralized UHR upper MAC, the allocation method of MLD ID+AID is described with examples respectively.

[0127] Figure 16 is a schematic diagram of a UHR non-AP MLD roaming scenario under a distributed UHR upper MAC architecture provided by an embodiment of the present application. As shown in Figure 16, the UHR AP MLD includes a controller and multiple EHT AP MLDs. The UHR AP MLD assigns unique MLD ID information: 1, 2...n to each EHT AP MLD, thereby obtaining EHT AP MLD 1, EHT AP MLD 2, ..., EHT AP MLD n. As shown in Figure 16, the implementation process of the UHR non-AP MLD roaming scenario under the distributed UHR upper MAC architecture includes the following steps:

[0128] Step 1: At location 1, UHR non-AP MLD 1 sends a (re)association request frame to EHT AP MLD 1 to initiate a request to establish a connection between the two links. EHT AP MLD 1 sends a (re)association response frame as shown in Figure 11, assigning the UHR AID information as<MLD ID1,AID1> .

[0129] Step 2: When UHR non-AP MLD 1 roams from location 1 to location 2, UHR non-AP MLD 1 sends a (re)association request frame as shown in FIG11 to EHT AP MLD 2, and carries UHR AID=<MLD ID1,AID1> information.

[0130] Step 3: After receiving the (Re)association request frame in step 2, EHT AP MLD2 sends a context retrieval request of AID1 to EHT AP MLD1 in the backhaul network.

[0131] Step 4: In the backhaul network, EHT AP MLD1 sends a context retrieval response of AID1 to EHT AP MLD2, including relevant context information.

[0132] In step 5, EHT AP MLD2 applies the context information of AID1 to the local device and sends a (re)association response frame shown in FIG11 to UHR non-AP MLD1, assigning UHR AID information MLD ID2+AID2 to UHR non-AP MLD1.

[0133] Step 6: EHT AP MLD1 reclaims AID1.

[0134] Step 7: The roaming process ends, and the EHT AP MLD2 directly exchanges encrypted data with the UHR non-AP MLD1.

[0135] In one example, Figure 17 is a schematic diagram illustrating the implementation of UHR AID allocation and recovery in a centralized UHR upper MAC architecture according to an embodiment of the present application. As shown in Figure 17 , the UHR AP MLD includes a UHR Upper MAC and multiple EHT AP MLDs. The UHR AP MLD assigns unique MLD ID information to each EHT AP MLD: 1, 2, ... n, resulting in EHT AP MLD 1, EHT AP MLD 2, ..., EHT AP MLD n. As shown in Figure 17 , the UHR AID allocation and recovery process in the centralized UHR upper MAC architecture includes the following steps:

[0136] Step 1: At location 1, UHR non-AP MLD 1 initiates a multi-link connection request to EHT AP MLD1 and EHT AP MLD2 on link 1. The request contains<MLD ID1,Link1> and<MLD ID2,Link2> link information.

[0137] Step 2: EHT AP MLD1 and EHT AP MLD2 negotiate an unassigned AID=1 through the backhaul network.

[0138] Step 3: EHT AP MLD1 sends a multi-link connection response frame as shown in FIG11 on link 1. The multi-link connection response frame includes the first UHR AID allocated by EHT AP MLD1 to UHR non-AP MLD1, i.e.<MLD ID1,AID1> information.

[0139] In step 4, when UHR non-AP MLD 1 roams from location 1 to location 2, UHR non-AP MLD 1 sends an ML reconfiguration request message as shown in Figures 14 and 15 to EHT AP MLD 2 on link 2. The request message carries the allocated UHR AID information, adds link 3 located at EHT AP MLD n, and deletes link 1 located at EHT AP MLD 1.

[0140] In step 5, EHT AP MLD2 and EHT AP MLD3 negotiate through the backhaul network and still assign AID=1 to UHR non-AP MLD 1.

[0141] Step 6: UHR non-AP MLD1 sends an ML reconfiguration response message to EHT AP MLD2 on link 2. The response message includes the second UHR AID, i.e.<MLD ID2,AID1> allocation information.

[0142] Step 7: EHT AP MLD1 negotiates with EHT AP MLD2 on the backhaul link, and EHT AP MLD1 recovers the first UHR AID, i.e.<MLD1,AID1> allocation information.

[0143] In step 8, UHR non-AP MLD1 roaming is completed, and data is exchanged with UHR AP MLD through link 2 and link 3.

[0144] In step 9, UHR non-AP MLD1 disconnects from UHR AP MLD, and EHT AP MLD2 and EHT AP MLD3 negotiate to reclaim AID1.

[0145] In one embodiment, FIG18 is a block diagram of an information distribution device provided by an embodiment of the present application. This embodiment is applied to a first network device. As shown in FIG18 , the information distribution device in this embodiment includes: a receiver 510 and a recovery module 520.

[0146] The receiver 510 is configured to receive a unique multi-link device identifier allocated by a second network device when a first network device accesses a network system where a second network device is located.

[0147] The reclaiming module 520 is configured to trigger the second network device to reclaim the multi-link device identifier when the first network device goes offline from the network system where the second network device is located.

[0148] In one embodiment, when a terminal device establishes an initial connection with a second network device through a first network device, the first network device allocates a first identifier to the terminal device.

[0149] In one embodiment, when the terminal device roams between at least two first network devices, the at least two first network devices cooperate to reallocate a first identifier to the terminal device and reclaim the last allocated first identifier.

[0150] In one embodiment, when the terminal device performs a partial link handover between at least two first network devices, the first identifier allocated to the terminal device remains unchanged.

[0151] In one embodiment, when the terminal device roams on multiple links of the same first network device, the first identifier allocated to the terminal device by the first network device remains unchanged.

[0152] In one embodiment, when the terminal device is disconnected from the second network device, the first network device reclaims the first identifier of the terminal device.

[0153] In one embodiment, the connection identifier in the first identifier allocated by the first network device to the terminal device is the same on multiple links.

[0154] In one embodiment, the first network device serving as the target device uses the first identifier to obtain the context information of the terminal device from the first network device serving as the source device.

[0155] In one embodiment, the context information includes at least one of the following: a frame sequence number; a frame number; target wake-up time negotiation information; block acknowledgement negotiation information, block acknowledgement scoreboard information, and PTK information.

[0156] In one embodiment, when at least two first network devices allocate a first identifier to a terminal device, if the at least two first network devices do not have the same connection identifier, establishment of a partial link between the terminal device and the second network device fails.

[0157] In one embodiment, the first identifier includes a multi-link device identifier and a connection identifier.

[0158] In one embodiment, the multi-link device identification includes one of the following: a MAC address of the first network device; or an identifier of the first network device.

[0159] In one embodiment, the information carried by the first identifier includes one of the following: a connection response frame; a connection request frame; a reconnection request frame; a reconnection response frame; a multilink reconfiguration request message; or a multilink reconfiguration response message.

[0160] In one embodiment, the frame bodies of the connection request frame, the connection response frame, the reconnection request frame, and the reconnection response frame include a first identifier field for indicating a first identifier allocated by the first network device to the terminal device.

[0161] In one embodiment, the status bitmap field in the multi-link reconfiguration message includes at least a connection identifier indication field, which is used to indicate whether the first identifier assigned by the first network device to the terminal device is carried; the public information field in the multi-link configuration message includes at least a first identifier field, which is used to indicate the first identifier assigned by the first network device to the terminal device.

[0162] In one embodiment, the reconnection request frame and the multilink reconfiguration request message both carry the first identifier allocated by the first network device to the terminal device;

[0163] Both the reconnection response frame and the multi-link reconfiguration response message carry the first identifier reallocated by the first network device to the terminal device.

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

[0165] In one embodiment, FIG19 is a block diagram of another information distribution apparatus provided by an embodiment of the present application. This embodiment is applied to a second network device. As shown in FIG19 , the information distribution apparatus in this embodiment includes: a distribution module 610 and a recovery module 620.

[0166] The allocation module 610 is configured to allocate a unique multi-link device identifier to the first network device when the first network device accesses the network system where the second network device is located;

[0167] The recovery module 620 is configured to recover the multi-link device identifier corresponding to the first network device when the first network device goes offline from the network system where the second network device is located.

[0168] The information distribution device provided in this embodiment is configured to implement the information distribution method applied to the second network device in the embodiment shown in FIG. 7 . The implementation principle and technical effects of the information distribution device provided in this embodiment are similar and will not be described in detail here.

[0169] In one embodiment, FIG20 is a block diagram of another information distribution device provided by an embodiment of the present application. This embodiment is applied to a terminal device. As shown in FIG20 , the information distribution device in this embodiment includes: a receiver 710.

[0170] The receiver 710 is configured to receive a first identifier allocated by the first network device when a terminal device establishes an initial connection with a second network device through the first network device.

[0171] In one embodiment, when roaming occurs between at least two first network devices, the terminal device receives a first identifier reallocated by the at least two first network devices.

[0172] In one embodiment, when the terminal device performs a partial link handover between at least two first network devices, the first identifier allocated to the terminal device by the at least two first network devices remains unchanged.

[0173] In one embodiment, when the terminal device roams on multiple links of the same first network device, the first identifier allocated to the terminal device by the first network device remains unchanged.

[0174] In one embodiment, when the terminal device is disconnected from the second network device, the first network device reclaims the first identifier of the terminal device.

[0175] In one embodiment, the connection identifier in the first identifier allocated by the first network device to the terminal device is the same on multiple links.

[0176] In one embodiment, when roaming occurs between at least two first network devices, the information distribution apparatus applied to the terminal device further includes:

[0177] a transmitter configured to send the allocated first identifier to the first network device as the target device, so that the first network device as the target device obtains the context information of the terminal device from the first network device as the source device using the allocated first identifier;

[0178] The receiver 710 is further configured to receive the first identifier reallocated by the first network device serving as the target device.

[0179] In one embodiment, the context information includes at least one of the following: a frame sequence number; a frame number; target wake-up time negotiation information; block acknowledgement negotiation information, block acknowledgement scoreboard information, and PTK information.

[0180] In one embodiment, when at least two first network devices allocate a first identifier to a terminal device, if the at least two first network devices do not have the same connection identifier, establishment of a partial link between the terminal device and the second network device fails.

[0181] In one embodiment, the first identifier includes a multi-link device identifier and a connection identifier.

[0182] In one embodiment, the multi-link device identification includes one of the following: a MAC address of the first network device; or an identifier of the first network device.

[0183] In one embodiment, the information carried by the first identifier includes one of the following: a connection response frame; a connection request frame; a reconnection request frame; a reconnection response frame; a multilink reconfiguration request message; or a multilink reconfiguration response message.

[0184] In one embodiment, the frame bodies of the connection request frame, the connection response frame, the reconnection request frame, and the reconnection response frame include a first identifier field for indicating a first identifier allocated by the first network device to the terminal device.

[0185] In one embodiment, the state bitmap field in the multi-link reconfiguration request message and the multi-link reconfiguration response message includes at least a connection identifier indication field, which is used to indicate whether the first identifier allocated by the first network device to the terminal device is carried;

[0186] The common information field in the multi-link reconfiguration request message and the multi-link reconfiguration response message includes at least a first identifier field, which is used to indicate a first identifier allocated by the first network device to the terminal device.

[0187] In one embodiment, the reconnection request frame and the multilink reconfiguration request message both carry the first identifier allocated by the first network device to the terminal device;

[0188] Both the reconnection response frame and the multi-link reconfiguration response message carry the first identifier reallocated by the first network device to the terminal device.

[0189] The information distribution device provided in this embodiment is configured to implement the information distribution method applied to a terminal device according to the embodiment shown in FIG8 . The implementation principle and technical effects of the information distribution device provided in this embodiment are similar and will not be described in detail here.

[0190] 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 810, a memory 820, and a communication interface 830. The number of processors 810 in the device can be one or more, and Figure 21 uses one processor 810 as an example. The number of memories 820 in the device can be one or more, and Figure 21 uses one memory 820 as an example. The processor 810, memory 820, and communication interface 830 of the device can be connected via a bus or other means, and Figure 21 uses a bus connection as an example. In this embodiment, the device can be a first network device.

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

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

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

[0194] In the case where the communication device is a terminal device, the device provided above can be configured to execute the information distribution method applied to the terminal device provided in any of the above embodiments, and have corresponding functions and effects.

[0195] An embodiment of the present application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform an information distribution method applied to a first network device. The method includes: when the first network device accesses a network system where a second network device is located, receiving a unique multi-link device identifier assigned by the second network device; when the first network device goes offline from the network system where the second network device is located, triggering the second network device to reclaim the multi-link device identifier.

[0196] An embodiment of the present application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform an information distribution method applied to a second network device. The method includes: when a first network device accesses a network system where a second network device is located, allocating a unique multi-link device identifier to the first network device; when the first network device goes offline from the network system where the second network device is located, reclaiming the multi-link device identifier corresponding to the first network device.

[0197] An embodiment of the present application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to execute an information distribution method applied to a terminal device. The method includes: when a terminal device establishes an initial connection with a second network device through a first network device, receiving a first identifier assigned by the first network device.

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

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

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

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

Claims

1. An information distribution method, applied to a first network device, comprising: When a first network device accesses a network system where a second network device is located, receiving a unique multi-link device identifier assigned by the second network device; When the first network device goes offline from the network system where the second network device is located, the second network device is triggered to reclaim the multi-link device identifier.

2. The method according to claim 1, wherein: When a terminal device establishes an initial connection with the second network device via the first network device, the first network device allocates a first identifier to the terminal device.

3. The method according to claim 2, wherein: When the terminal device roams between at least two first network devices, the at least two first network devices collaborate to reallocate a first identifier for the terminal device and recycle the first identifier allocated last time.

4. The method according to claim 2, wherein: When the terminal device performs partial link switching between at least two first network devices, the first identifier allocated to the terminal device remains unchanged.

5. The method according to claim 2, wherein: When the terminal device roams on multiple links of the same first network device, the first identifier allocated to the terminal device by the first network device remains unchanged.

6. The method according to claim 2, wherein: When the terminal device is disconnected from the second network device, the first network device recycles the first identifier of the terminal device.

7. The method according to claim 2, wherein: The connection identifier in the first identifier allocated by the first network device to the terminal device is the same on multiple links.

8. The method according to claim 2, wherein: The first network device as the target device uses the first identifier to obtain the context information of the terminal device in the first network device as the source device.

9. The method according to claim 8, wherein: The context information includes at least one of the following: frame sequence number; frame number; target wake-up time negotiation information; block confirmation negotiation information, block confirmation scoreboard information and temporary pairwise transmission key PTK information.

10. The method according to claim 2, wherein: When at least two of the first network devices allocate the first identifier to the terminal device and when there is no identical connection identifier between the at least two first network devices, establishment of a portion of the links between the terminal device and the second network device fails.

11. The method according to any one of claims 2 to 10, wherein: The first identifier includes the multi-link device identifier and a connection identifier.

12. The method according to claim 1, wherein: The multi-link device identification includes one of the following: a media access control MAC address of the first network device; and a first network device identifier.

13. The method according to any one of claims 2 to 10, wherein: The bearer information of the first identifier includes one of the following: connection response frame; connection request frame; reconnection request frame; reconnection response frame; multilink reconfiguration request message; multilink reconfiguration response message; basic service set BSS transfer management request frame; BSS transfer management response frame.

14. The method according to claim 13, wherein: The frame bodies of the connection request frame, the connection response frame, the reconnection request frame and the reconnection response frame include a first identifier field for indicating a first identifier allocated by the first network device to the terminal device.

15. The method according to claim 13, wherein: The state bitmap field in the multi-link reconfiguration request message and the multi-link reconfiguration response message at least includes a connection identifier indication field, which is used to indicate whether the first identifier allocated by the first network device to the terminal device is carried; The common information field in the multi-link reconfiguration request message and the multi-link reconfiguration response message includes at least a first identifier field, which is used to indicate a first identifier allocated by the first network device to the terminal device.

16. The method according to claim 13, wherein: The reconnection request frame and the multilink reconfiguration request message both carry the first identifier allocated by the first network device to the terminal device; The reconnection response frame and the multi-link reconfiguration response message both carry the first identifier reallocated by the first network device to the terminal device.

17. An information distribution method, applied to a second network device, comprising: When a first network device accesses a network system where a second network device is located, allocating a unique multi-link device identifier to the first network device; When the first network device goes offline from the network system where the second network device is located, the multi-link device identifier corresponding to the first network device is recovered.

18. An information distribution method, applied to a terminal device, comprising: When a terminal device establishes a first connection with a second network device via a first network device, a first identifier assigned by the first network device is received.

19. The method according to claim 18, in the case where roaming occurs between at least two of the first network devices, the method further comprises: The first network device as the target device sends the allocated first identifier to the first network device as the source device, so that the first network device as the target device uses the allocated first identifier to Acquire the context information of the terminal device from the device; A first identifier reallocated by the first network device serving as the target device is received.

20. 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 16, 17 or 18 to 19.

21. 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 16, 17 or 18 to 19.

Images