Information distribution method and device and storage medium

Abstract

The invention provides an information distribution method and device and a storage medium. The information distribution method applied to a first network device comprises the following steps: receiving a unique multi-link device identifier distributed by a second network device under the condition that the first network device accesses a network system where the second network device is located; and under the condition that the first network equipment is offline from the network system in which the second network equipment is located, triggering the second network equipment to recycle the multi-link equipment identifier.

Description

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] Under the framework of two types of non-collocated Access Point Multi-Link Devices (non-collocated AP MLD) (also known as Ultra High Reliability Access Point Multi-Link Device (UHR AP MLD)), on the one hand, each UHR AP MLD can allocate a network-wide unique association identifier (AID) to each UHR non-AP MLD; on the other hand, the UHR AP MLD may contain multiple Extremely-High Throughput Access Point Multi-Link Device (EHT AP MLD) physical nodes. Especially in large-scale enterprise networks and public networks, the number of EHT AP MLD nodes is in the hundreds to tens of thousands, and each EHT AP MLD can provide services for dozens of non-AP MLDs at the same time. If the traditional 16-bit AID is still used to indicate each UHR non-AP MLD, AID indication conflicts are likely to occur. Summary of the invention

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

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

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

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

[0007] The embodiment of the present application provides an information distribution method, which is applied to a second network device, including:

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

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

[0010] The embodiment of the present application provides an information distribution method, which is applied to a terminal device, including:

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

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

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

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

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

[0016] Figure 1 This is a schematic diagram of the format configuration of an AID field provided by the prior art;

[0017] Figure 2 This is a schematic diagram of a format configuration of a TIM field provided by the prior art;

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

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

[0020] Figure 5 It is a configuration diagram of a distributed UHR AP MLD architecture provided by the prior art;

[0021] Figure 6 is a flow chart of an information distribution method provided in an embodiment of the present application;

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

[0023] Figure 8 is a flow chart of another information distribution method provided in an embodiment of the present application;

[0024] Fig. 9 It is a schematic diagram of a process of allocating and recovering a multi-link device identifier and a first identifier provided by an embodiment of the present application;

[0025] Fig.10 It is a format configuration diagram of a UHR AID information element provided in an embodiment of the present application;

[0026] Fig.11 It is a configuration diagram of a multi-link (re)connection request / response frame provided in an embodiment of the present application;

[0027] Fig.12 It is a configuration diagram of a state bitmap subfield in a multi-link reconfiguration message provided by the prior art;

[0028] Fig.13 It is a configuration diagram of a common information field in a multi-link reconfiguration message provided by the prior art;

[0029] Fig.14 It is a schematic diagram of an extended configuration of a status bitmap subfield in a multilink reconfiguration message provided by an embodiment of the present application;

[0030] Fig.15 It 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;

[0031] Fig.16 It 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;

[0032] Fig.17 It is a schematic diagram of implementing UHR AID allocation and recovery under a centralized UHR upper MAC architecture provided by an embodiment of the present application;

[0033] Fig.18 is a structural block diagram of an information distribution device provided in an embodiment of the present application;

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

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

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

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

[0038] In a Basic Service Set (BSS) network, the AID field contains a 16-bit value specified by the Access Point (AP) during the connection process, which can uniquely identify the information of a connected terminal (Station, STA). In a Mesh Basic Service Set (MBSS) network, the AID is assigned by a Mesh Station (Mesh STA) to another Mesh STA. Figure 1 This is a schematic diagram of the format configuration of an AID field provided by the prior art, such as Figure 1 As shown, each AID occupies 2 bytes.

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

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

[0041] AID is widely used in functions such as channel status (sounding) collection, trigger frame (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:

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

[0043] (2) Unicast Buffer Indication: In the beacon frame sent by the AP containing the Traffic Indication Message (TIM) field, the AP uses the AID information to indicate the buffer status of each STA. Figure 2 FIG. 1 is a schematic diagram of a format configuration of a TIM field provided by the prior art. Figure 2As shown in the figure, the Element ID field is used to fill the identifier of the TIM field; Length is used to indicate the length of the field; DTIM Counter is used to indicate the count of beacon frames (Beacon) before the delivery traffic indication message (DTIM) appears in the field, where DTIM Count is 0, indicating that the TIM is DTIM, and other values ​​indicate that the field is TIM; DTIM period is used to indicate the frequency of occurrence of the field (an integer multiple of the Beacon period); Bitmap control contains the control information of the AID; The length of the PartialVirtual Bitmap field is 0--251 bytes, and each bit in the Partial Virtual Bitmap field is used to indicate whether there is a corresponding STA unicast data cache information, indicating cache information when the bit is 1, and no cache when the bit is 0, indicating cache information of a maximum of 2007 STAs.

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

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

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

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

[0048] Another distributed UHR AP MLD architecture is proposed in the Seamless Roaming for UHR solution. Figure 5 FIG. 1 is a configuration diagram of a distributed UHR AP MLD architecture provided by the prior art. Figure 5 As shown in the figure, 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 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.

[0049] The embodiment of the present application provides an information allocation method under two UHR AP MLD architectures (i.e., the UHRAP MLD architecture of the centralized UHR upper MAC and the distributed UHR AP MLD architecture), which can allocate UHR AID to each UHR non-AP MLD through UHR AP MLD, thereby solving the problem of AID conflict indication caused by insufficient AID resources in the prior art. At the same time, the information allocation method proposed in the present application is compatible with traditional single-link STA and EHT non-AP MLD, and is compatible with the current function of using AID to uniquely identify STA in the sounding process, Trigger frame and TIM field.

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

[0051] In one embodiment, Figure 6 1 is a flow chart of an information allocation method provided in an embodiment of the present application. This embodiment is applied to the case where a first identifier is automatically allocated to a non-AP MLD under a UHR AP MLD architecture. This embodiment can be executed by a first network device. Figure 6 As shown, this embodiment includes: S110-S120.

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

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

[0054] In one example, the network system where the second network device is located 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 is located, the second network device allocates a multi-link device identifier unique to the entire network to the newly connected first network device. After a first network device goes offline from the network system where the second network device is located, the second network device recovers the multi-link device identifier allocated to the offline first network device.

[0055] 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, which can ensure that each first network device uniquely identifies each terminal device using the first identifier.

[0056] 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 recycle the first identifier that was previously allocated. 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 recycle the first identifier that was previously allocated. The first identifier includes a multi-link device identifier and a connection identifier. The first identifier that is reallocated to the terminal device through negotiation between 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, which can ensure that each first network device uniquely identifies each terminal device using the first identifier.

[0057] In one embodiment, when a terminal device switches a portion of its links 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 portion of its links 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 one example, when a terminal device switches all links 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, and at this time, it is not necessary to notify the terminal device through signaling that its multi-link device identifier has changed.

[0058] 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. Each first network device may include multiple links, and when the 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.

[0059] 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. In one example, when the terminal device establishes a connection with the second network device through multiple first network devices, when the terminal device is disconnected from the second network device, multiple first network devices belonging to the same second network device reclaim the allocated first identifier. In one example, when the terminal device establishes a connection with the second network device through a first network device, when the terminal device is disconnected from the second network device, the first network device reclaims the first identifier allocated to the terminal device.

[0060] 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. When a terminal device establishes a connection with a second network device through at least one first network device, multiple first network devices on the relevant link negotiate to allocate a first identifier to the terminal device, and the connection identifier on each link of the terminal device is the same.

[0061] In one embodiment, 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. 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 uses the first identifier to obtain the context information of the terminal device from the first network device as the source device, and applies it to the first network device as the target device, and 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.

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

[0063] 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, the 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, and if the at least two first network devices cannot negotiate a common unallocated connection identifier through the backhaul link, the establishment of some links between the terminal device and the second network device fails.

[0064] 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; a first network device identifier. The first network device identifier may be an index value of the first network device.

[0065] In one embodiment, the bearer information of 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, and a BSS Transition Management (BTM) request / response frame. The connection response frame and the connection request frame are paired; the reconnection request frame and the reconnection response frame are paired; the multilink reconfiguration request message and the multilink reconfiguration response message are paired.

[0066] In one embodiment, the frame body of the connection request frame, the connection response frame, the reconnection request frame, and the 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, and the first identifier field includes a multi-link device identification field and a connection identifier field, the multi-link device identification field is used to indicate a multi-link device identification assigned by the second network device to the first network device; the connection identifier field is used to indicate 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.

[0067] In one embodiment, the status 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 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 at least includes 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.

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

[0069] 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 is 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 is 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.

[0070] In one embodiment, Figure 7 1 is a flow chart of another information allocation method provided by an embodiment of the present application. This embodiment is applied to the case where a first identifier is automatically allocated to a non-AP MLD under a UHR AP MLD architecture. This embodiment can be executed by a second network device. Figure 7 As shown, this embodiment includes: S210-S220.

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

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

[0073] In one example, after a new first network device accesses the network system where the second network device is located, the second network device allocates a multi-link device identifier unique to the entire network to the newly connected first network device. After a first network device goes offline from the network system where the second network device is located, the second network device reclaims the multi-link device identifier allocated to the offline first network device.

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

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

[0076] S310: When a terminal device establishes an initial connection with a second network device through a first network device, a first identifier allocated by the first network device is received.

[0077] 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 cooperation.

[0078] In one embodiment, when the terminal device performs partial link switching 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.

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

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

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

[0082] 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 in the first network device as the source device by using the allocated first identifier;

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

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

[0085] 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 confirmation negotiation information, block confirmation scoreboard information, and PTK information.

[0086] In one embodiment, when at least two first network devices allocate a first identifier to a terminal device, if 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.

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

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

[0089] In one embodiment, the bearer information of 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.

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

[0091] In one embodiment, the state bitmap field in the multilink reconfiguration request message and the multilink 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;

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

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

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

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

[0096] It should be noted that, for 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, please refer to the corresponding description in the above-mentioned information allocation method applied to the first network device, and will not be repeated here.

[0097] In the following embodiments, 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.

[0098] In one example, Fig. 9 1 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. Fig. 9 As shown, the allocation process and the recovery process of the multi-link device identifier and the first identifier in this embodiment include:

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

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

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

[0102] 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-APMLD 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.

[0103] 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 for the UHR non-AP MLD.

[0104] When a UHR non-AP MLD roams between at least two links of an EHT AP MLD, an EHTAP MLD configures a second UHR AID for the UHR non-AP MLD and recycles the first UHR AID; when a UHR non-APMLD 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, multiple EHT AP MLDs configure a second UHR AID for the UHR non-AP MLD through negotiation and recycle the first UHRAID. The update of the UHR AID includes the update of the EHT AP MLD ID in the UHR AID, or the update of the suffix AID, 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.

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

[0106] 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 APMLD, then one EHT AP MLD reclaims the UHR AID of the UHR non-AP MLD; if the UHRnon-AP MLD establishes a connection with the UH AP MLD through multiple EHT AP MLDs, then multiple EHT AP MLDs collaborate to reclaim the UHR AID of the UHRnon-AP MLD.

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

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

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

[0110] In some application examples, the UHR AP MLD completes the allocation and recovery of the MLD ID for each EHT AP MLD through the backhaul network.

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

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

[0113] In some application instances, when the 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. At this time, it may not be necessary to notify the UHR non-AP MLD of the change of its EHT MLD ID through signaling.

[0114] In some application instances, when the 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 one EHT AP MLD, these EHT AP MLDs negotiate a common unallocated 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 unallocated AID of EHT AP MLD1, EHT AP MLD2, and EHT AP MLD3), and sends the AID to the UHR non-AP MLD through a (re)association response frame.

[0115] In some application instances, when the 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 failure to establish some links (for example, when the UHR non-AP MLD sends a (re)association request frame ((re)association request frame) on the link to which the first EHT AP MLD belongs, and establishes 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 not assigned to the first EHT AP MLD and the second EHT AP MLD, but AID=100 has been assigned to other terminal devices in the third EHT AP MLD), the first UHR AP MLD sends the AID to the UHR non-AP MLD through a (re)association response frame, and the (Re)association response frame carries a connection rejection link located in the third EHT AP MLD.

[0116] 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 UHR AID update information. For example, the UHR non-AP MLD sends a Figure 3-4 On the return link, the second EHT AP MLD uses the UHR AID to obtain the context information of the UHR non-AP MLD from the first EHTAP MLD, such as the frame sequence number (SN), frame number (PN packet number), target wake-up time (TWT) negotiation, block confirmation (BA) negotiation, PTK and other information, and applies them to the second EHT AP MLD. The second EHT AP MLD sends a (Re) association response frame to the UHR non-AP MLD, including the latest allocated UHR AID.

[0117] 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 recycle the first UHR AID.

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

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

[0120] In one example, Fig.10 FIG. 1 is a schematic diagram of a format configuration of a UHR AID information element provided in an embodiment of the present application. In this example, the format of the UHR AID information element is as follows: Fig.10 The meaning of each field is shown in Table 1.

[0121] Table 1 Meaning of UHR AID element field

[0122]

[0123] Fig.11 Schematic diagram of a configuration of a multi-link (re)connection request / response frame provided in an embodiment of the present application. Fig.11 As shown, the (Re)association request / response frame carries Fig.10 Parameters of the UHR AID element format as shown.

[0124] Fig.12 The present invention is a configuration diagram of a status bitmap subfield in a multi-link reconfiguration message provided by the prior art. Fig.13 FIG. 1 is a configuration diagram of a common information field in a multi-link reconfiguration message provided by the prior art. Fig.12 As shown in FIG. 1 , the Present Bitmap subfield provided in the ML reconfiguration action frame is used to indicate whether the ML reconfiguration message carries the MLD MAC address, the EML capability set, the MLD capability set, and other information. Fig.13As shown, the common information field (Common Infofield) includes the specific contents of the MLD MAC address, the EML capability set and the MLD capability set and other information (if carried).

[0125] Fig.14 This 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. Fig.15 The following is a schematic diagram of an extended configuration of a common information field in a multi-link reconfiguration message provided by an embodiment of the present application. For a multi-link reconfiguration (ML Reconfiguration) message, the extended formats of the presence bitmap subfield (Presence Bitmap subfield) and the common information field (Common Info field) in the ML Reconfiguration are as follows: Fig.14 and Fig.15 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 multilink device identification field (MLD ID field) and a connection identifier field (AID field) are included in the UHR AID field. In one embodiment, the multilink reconfiguration message includes a multilink reconfiguration request message and a multilink reconfiguration response message.

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

[0127] Fig.16 FIG. 1 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. Fig.16 As shown, the UHR AP MLD includes a controller and multiple EHT AP MLDs. The UHR AP MLD assigns unique MLD ID information to each EHT AP MLD: 1, 2...n, that is, EHT AP MLD 1, EHT AP MLD 2, ..., EHT AP MLD n are obtained. Fig.16 As shown in FIG. 1 , 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 (i.e., Location 1), UHR non-AP MLD 1 sends a (re)association request frame to EHT AP MLD1 to initiate a request to establish two link connections. EHT AP MLD1 sends a (re)association response frame as shown in 11, and the assigned UHR AID information is<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 Fig.11 The (re)association request frame shown in FIG. 1 carries UHR AID=<MLD ID1,AID1> information.

[0130] Step 3: After receiving the (Re)association request frame in step 2, EHT APMLD2 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] Step 5: EHT AP MLD2 applies the context information of AID1 to the local device and sends it to UHR non-APMLD1. Fig.11 The (re)association response frame shown here indicates that the UHR non-AP MLD1 allocates the UHR AID information as MLD ID2+AID2.

[0133] Step 6: EHT AP MLD1 recycles 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, Fig.17 FIG. 1 is a schematic diagram of an implementation of UHRAID allocation and recovery under a centralized UHR upper MAC architecture provided by an embodiment of the present application. Fig.17As shown, the UHR AP MLD includes a UHR Upper MAC and multiple EHTAP MLDs. The UHR AP MLD allocates unique MLD ID information to each EHT AP MLD: 1, 2...n, that is, EHTAP MLD 1, EHT AP MLD 2, ..., EHT AP MLD n are obtained. Fig.17 As shown, the allocation and recovery process of UHR AID under the centralized UHR upper MAC architecture includes the following steps:

[0136] Step 1: At position 1, UHR non-AP MLD 1 initiates a multi-link connection request to EHT AP MLD1 and EHTAP 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 unallocated AID=1 through the backhaul network.

[0138] Step 3: EHT AP MLD1 sends the following message on link 1: Fig.11 The multi-link connection response frame shown in FIG. 1 includes the first UHR AID allocated by EHT AP MLD1 to UHR non-AP MLD 1, that is,<MLD ID1,AID1> information.

[0139] Step 4: When UHR non-AP MLD 1 roams from location 1 to location 2, UHR non-AP MLD 1 sends the following message to EHT AP MLD 2 on link 2: Fig.14 and Fig.15 The ML reconfiguration request message shown carries the allocated UHR AID information, adds link 3 located in EHT AP MLD n, and deletes link 1 located in EHT AP MLD1.

[0140] Step 5: EHT AP MLD2 and EHT AP MLD3 negotiate through the backhaul network and still allocate AID=1 to UHRnon-AP MLD 1.

[0141] Step 6: UHR non-AP MLD1 sends an ML reconfiguration response message to EHT AP MLD2 on link2. 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 reclaims the first UHRAID, i.e.<MLD1,AID1> allocation information.

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

[0144] 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, Fig.18 is a structural block diagram of an information distribution device provided in an embodiment of the present application. This embodiment is applied to a first network device. Fig.18 As shown, 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 assigned by a second network device when a first network device accesses a network system where a second network device is located.

[0147] The recovery module 520 is configured to trigger the second network device to recover 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 via 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 for the terminal device and recycle the last allocated first identifier.

[0150] In one embodiment, when the terminal device performs a partial link switch 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 recycles the first identifier of the terminal device.

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

[0154] In one embodiment, 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.

[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 confirmation negotiation information, block confirmation 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 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.

[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 bearer information of 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.

[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 that the first network device has allocated 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 Figure 6The information distribution method applied to the first network device in the illustrated embodiment is similar to the implementation principle and technical effect of the information distribution device provided in this embodiment, which will not be described in detail here.

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

[0166] An allocation module 610 is configured to allocate a unique multi-link device identifier to a first network device when the first network device accesses a network system where a 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 Figure 7 The information distribution method applied to the second network device in the illustrated embodiment is similar to the implementation principle and technical effect of the information distribution device provided in this embodiment, and will not be described in detail here.

[0169] In one embodiment, Fig. 20 1 is a structural block diagram of another information distribution device provided in an embodiment of the present application. This embodiment is applied to a terminal device. Fig. 20 As shown, 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 partial link switching 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 recycles the first identifier of the terminal device.

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

[0176] In one embodiment, when roaming occurs between at least two first network devices, the information distribution device 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 in the first network device as the source device using the allocated first identifier;

[0178] The receiver 710 is further configured to receive a first identifier reallocated by the first network device serving as a 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 confirmation negotiation information, block confirmation 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 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.

[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 bearer information of 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.

[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 multilink reconfiguration request message and the multilink 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 that the first network device has allocated 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 Figure 8 The information distribution method applied to the terminal device in the illustrated embodiment is similar to the implementation principle and technical effect of the information distribution device provided in this embodiment, which will not be described in detail here.

[0190] In one embodiment, Fig.21 Schematic diagram of a communication device provided in an embodiment of the present application. Fig.21 As shown, the device provided by the present application includes: a processor 810, a memory 820 and a communication interface 830. The number of processors 810 in the device can be one or more. Fig.21 In the example, a processor 810 is used. The number of memories 820 in the device may be one or more. Fig.21 A memory 820 is taken as an example. The processor 810, the memory 820 and the communication interface 830 of the device can be connected via a bus or other means. Fig.21 In the example, the bus connection is used. In this embodiment, the device may 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, an application required for at least one function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 820 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 820 may further include a memory remotely arranged relative to the processor 810, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. 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 the computer executable instructions are executed by a computer processor, they are used to execute an information distribution method applied to a first network device. The method includes: 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, 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 the computer executable instructions are executed by a computer processor, they are used to execute 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, a unique multi-link device identifier is allocated 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.

[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 comprising: when a terminal device establishes an initial connection with a second network device through a first network device, receiving a first identifier allocated 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 can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, microprocessor or other computing device, although the present application is not limited thereto.

[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 have any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory devices and systems (digital versatile discs (DVD) or compact disks (CD)), etc. Computer-readable media may include non-transient storage media. A data processor may be any type suitable for the local technical environment, such as but not limited to a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FGPAs) and a processor based on a multi-core processor architecture.

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

Claims

1. An information distribution method, characterized in that: 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, characterized in that 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, characterized in that 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, characterized in that: 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, characterized in that: 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, characterized in that 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, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that In the case where at least two of the first network devices allocate the first identifier to the terminal device, if 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, characterized in that: The first identifier includes the multi-link device identifier and a connection identifier.

12. The method according to claim 1, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that 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 to carry the first identifier allocated by the first network device to the terminal device; 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, characterized in that 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, characterized in that: Applied to the 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, characterized in that: Applied to terminal equipment, including: 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, characterized in that In the case where roaming occurs between at least two of the first network devices, the method further includes: 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 in the first network device as the source device by using the allocated first identifier; A first identifier reallocated by a first network device as a target device is received.

20. A communication device, characterized in that: include: memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-16, 17 or 18-19.

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

Images