Mesh wireless local area network discovery using multi-link operation

Abstract

A method of configuring a mesh multi-link device (MLD) operating in a mesh network using multi-link operation (MLO), the mesh network comprising a plurality of mesh STAs and mesh MLDs, the MLD communicating over a plurality of WLAN wireless links between one or more AP MLDs and one or more non-AP MLDs, wherein each MLD has one or more affiliated STAs, each affiliated STA operating on a different link designated for mesh operation; the method comprising: receiving MLO mesh basic service set (MBSS) information indicating multi-link operation mesh basic service set (MLO MBSS) capabilities and / or operating parameters; wherein a specific mesh multi-link element (MLE) is included in the MLO MBSS information, the specific MLE being used to advertise mesh capabilities of the MLD.

Description

Technical Field

[0001] This disclosure generally relates to methods and systems in the field of WLAN mesh operation. Background Technology

[0002] A Basic Service Set (BSS) is a group of sites defined by IEEE 802.11 that can communicate with each other directly (e.g., in a mesh network) or through Access Points (APs) (i.e., the infrastructure BSS). It is the basic network building block of IEEE 802.11 WLANs.

[0003] When a mesh STA that does not support Infrastructure Basic Services Set (BSS) initiates a connection to a mesh basic services set (MBSS) (i.e., a mesh network), it attempts to discover other mesh STAs and begins sending beacon frames advertising the MBSS. Other mesh STAs then use traditional discovery mechanisms from IEEE 802.11, such as:

[0004] Passively scan and listen for beacons or unsolicited probe response frames;

[0005] Actively scan and send probe request frames / receive probe response frames.

[0006] IEEE 802.11 defines the communication requirements for STAs operating in a mesh network. Mesh STAs discover and pair with each other to form mesh links. Data can be routed between peer mesh STAs via a series of hops through other STAs operating in the mesh network.

[0007] In a typical mesh architecture that can be implemented according to IEEE 802.11, information is exchanged between the mesh network and external infrastructure (e.g., BSS 1 at STA 1 or the LAN at STA 4). Mesh peer-to-peer links are associated links, for example, secure connections established between mesh STAs. These links typically reside in the same WLAN frequency band, such as 2.4 GHz.

[0008] IEEE 802.11be introduced the multi-link device (MLD). An MLD communicates with multiple WLAN wireless links between an AP MLD and a non-AP MLD. MLDs support traffic switching across multiple links, thus utilizing multiple channels to provide performance gains.

[0009] Specifically, each AP MLD can have one or more subordinate APs, where each subordinate AP operates on a different link. Similarly, each non-AP MLD has one or more subordinate non-AP STAs, where each subordinate non-AP STA operates on a different link.

[0010] IEEE 802.11be also introduces dynamic link switching, where traffic can move from one link to another because a non-AP STA belonging to a non-AP MLD can be in active or power-saving mode while running on one of the links.

[0011] The Reduced Neighbor Report (RNR) element in IEEE 802.11 is included in beacon frames and probe response frames and is defined as containing channel and other information about neighboring APs or APs belonging to AP MLDs that are sending beacon frames and probe response frames.

[0012] A Multi-Link Element (MLE) includes information corresponding to other links in the MLD. An AP or non-AP STA that sends a frame including an MLE belongs to that MLD. Summary of the Invention

[0013] Currently, IEEE 802.11be and its successor, IEEE 802.11bn, do very little in supporting multi-link operation (MLO) in mesh networks. Many aspects of mesh functionality need to be updated to handle MLO.

[0014] This disclosure attempts to mitigate this situation. This disclosure relates to the notification and discovery aspects of MLO MBSS.

[0015] This disclosure is defined by the scope of the independent claims. The dependent claims provide advantageous embodiments of this disclosure.

[0016] This disclosure provides:

[0017] A first aspect of a method for configuring a mesh multi-link device (MLD) is provided, wherein the MLD operates using multi-link operation (MLO) in a mesh network comprising multiple mesh STAs and mesh MLDs, the MLDs communicating via multiple WLAN wireless links between one or more AP MLDs and one or more non-AP MLDs, wherein each MLD has one or more affiliated STAs, each affiliated STA operating on a different link specified for the mesh operation; the method comprising: receiving MLO MBSS information indicating multi-link operation mesh basic service set (MLO MBSS) capabilities and / or operational parameters; wherein a specific mesh multi-link element (MLE) is included in the MLO MBSS information, and the mesh capabilities of the MLD are advertised using the specific MLE.

[0018] Therefore, based on the first aspect of the approach, a protocol for how MLDs discover peer-to-peer network MLDs was established.

[0019] According to the implementation of the method described in the first aspect, receiving MLO MBSS information indicating multi-link operation mesh basic service set (MLO MBSS) capability may include: receiving a beacon frame or a non-requested probe response frame; or receiving a probe response frame as a response to a requested probe request frame; or receiving a multi-link probe response as a response to a requested multi-link probe request.

[0020] According to the implementation of the method described in the first aspect, the method may further include: updating reduced neighbor report (RNR) elements and announcing the updated RNR elements in beacon frames and probe response frames, and announcing specific MLEs; updating mesh operations of one or more STAs belonging to the MLD, so that the MLD can announce and discover various MBSSs on the links specified for the mesh operations.

[0021] Therefore, according to these implementations, Mesh MLD should announce new Mesh variant multi-link elements (MLEs) in beacon frames and probe response frames, while updating existing reduced neighbor report (RNR) elements.

[0022] According to the implementation of the method described in the first aspect, the method may further include: configuring a specific MLE to advertise mesh capabilities, wherein configuring a specific MLE may include: extending a field in the MLE that indicates information shared by all links (Common Info field) through an element used to advertise mesh services (MeshConfiguration Element); updating a field in the MLE that indicates control over multiple links (Multi-Link Control field) by: extending a bitmap-containing subfield in the Multi-Link Control subfield (Presence Bitmap subfield) through an indicator indicating that the Mesh Configuration Element exists in the Common Info field (Mesh Configuration Element Present indicator); and further extending the Presence Bitmap subfield through an indicator indicating whether all links in the link have mesh capabilities.

[0023] Therefore, providing an updated MLE enables the mesh MLD to announce its MLO MBSS capabilities within the updated MLE.

[0024] According to the implementation of the method described in the first aspect, the method may further include: configuring a specific MLE to advertise mesh capabilities, wherein configuring a specific MLE may include: assigning a new type value in a subfield (Type subfield) of a subfield of the multi-link control subfield in the MLE, the new type value indicating that the specific MLE is used for mesh operation.

[0025] Therefore, providing this new type of MLE enables mesh MLDs to use the new mesh MLE to advertise their MLOMBSS capabilities.

[0026] According to the implementation of the method in the first aspect, the method may further include: updating the RNR element by including a subfield (Mesh Capable subfield) indicating that the link can be used for mesh operations, wherein the value of the Mesh Capable subfield is equal to 1 to indicate that the link can be used for mesh operations.

[0027] According to the implementation of the method in the first aspect, the method may further include: discovering a mesh MLO using mesh multilink probe requests and responses, wherein discovery may include: receiving information details of a peering mesh MLD prior to peering with another mesh MLD, wherein the information details received from the mesh MLD include a specific MLE with mesh capabilities, the specific MLE including a field (Link Info field) of link information corresponding to all other subordinate STAs operating in the mesh BSS or relating to a specific request from a subordinate STA operating in the mesh BSS.

[0028] Therefore, mesh multilink probe requests and responses can be used to discover MLOMBSS capabilities and parameters in mesh MLEs of peer mesh MLDs.

[0029] According to the implementation of the method described in the first aspect, in this method, the link information field can indicate which links support mesh operation and the corresponding mesh parameters.

[0030] According to the implementation of the method described in the first aspect, in this method, the mesh multi-link probe request may include a link information field, which indicates one or more specific affiliated STAs that need to respond.

[0031] According to the implementation of the method described in the first aspect, the method may further include: if all links of the MLD support mesh functionality, the updated public information field of the MLE is used to include a mesh configuration element and indicate that all links support mesh operation, wherein the mesh information included in the mesh configuration element applies to all links; otherwise, if only some links of the MLD support mesh functionality, information common to all mesh-enabled links of the MLD is included in the public information field of the MLD, while link-specific information is included in a sub-field (Per-STA Profile sub-element) of the link information field of the MLE indicating the STA profile, wherein the link-specific information is obtained by receiving a response to a mesh multi-link probe request from a peer MLD with mesh capability.

[0032] According to the implementation of the method described in the first aspect, the method may further include: if only some links in the MLD support mesh functionality, then the subfield in the Per-STA profile sub-element that indicates control over the STA (STA Control subfield) is updated to include a subfield indicating mesh parameters in the MeshCapable STA Info field and a subfield indicating mesh parameters in the Mesh Capable STA Profile field.

[0033] According to the implementation of the method described in the first aspect, the method may further include: if the value of the Mesh Capable Common subfield is equal to 0, then the value of the Mesh Capable STA Info subfield is equal to 1, which indicates that the link supports the mesh function and all mesh configuration information in the link-specific mesh configuration information is included in the updated MLE's STA Info subfield.

[0034] Therefore, the above method enables the traditional mesh configuration information in mesh configuration elements to be remapped into the MLD architecture, thereby providing public MLD mesh-specific information and MLD mesh link-specific information.

[0035] According to the implementation of the method described in the first aspect, the method may further include: if only some links in the MLD support mesh functionality, then the updated MLE includes a subfield indicating STA information (STAInfo subfield) including a TBTT Adjusting subfield and / or a Mesh Power Save Level subfield.

[0036] According to the implementation of the method described in the first aspect, in this method, the TBTT adjustment subfield and / or the mesh power saving level subfield will be removed from the mesh configuration element of the common subfield.

[0037] According to the implementation of the method described in the first aspect, the method may further include: if the mesh configuration files of each STA belonging to the corresponding mesh STA are the same, the method may further include: announcing the mesh capability of the MLD with mesh capability by updating the predefined mesh configuration elements.

[0038] According to the implementation of the method in the first aspect, the method may further include: a predefined mesh configuration element is updated by including a subfield for mesh capability extension (Mesh CapabilityExtension subfield), the mesh configuration element including a subfield indicating mesh capability (Mesh Capability subfield), wherein the last bit of the mesh capability subfield indicates whether the mesh configuration element is updated by the mesh capability extension subfield.

[0039] Therefore, this allows traditional mesh configuration elements to be updated to announce MLO MBSS capabilities.

[0040] This disclosure also provides a second aspect of a mesh multi-link device (MLD) for: operating in a mesh network using multi-link operation (MLO), the mesh network including multiple mesh STAs and mesh MLDs, communicating via multiple WLAN wireless links between one or more AP MLDs and one or more non-AP MLDs, wherein each MLD has one or more affiliated STAs, each affiliated STA being used to operate on a different link specified for the mesh operation; receiving MLO MBSS information indicating multi-link operation mesh basic service set (MLO MBSS) capabilities and / or operating parameters; wherein a specific mesh multi-link element (MLE) is included in the MLO MBSS information, and the mesh capabilities of the MLD are advertised using the specific MLE.

[0041] According to the implementation of the device described in the second aspect, the device may further include: an MLD for receiving MLO MBSS information indicating multi-link operation mesh basic service set (MLO MBSS) capabilities, wherein the MLD is used for:

[0042] Receive beacon frames or non-requested probe response frames; or receive probe response frames as a response to a requested probe request frame; or receive multilink probe responses as a response to a requested multilink probe request.

[0043] According to the implementation of the device described in the second aspect, the device may further include: an MLD for: updating reduced neighbor report (RNR) elements and announcing the updated RNR elements in beacon frames and probe response frames, and announcing specific MLEs; updating mesh operations of one or more STAs belonging to the MLD, such that the MLD can announce and discover various MBSSs on the links specified for the mesh operations.

[0044] According to the implementation of the device described in the second aspect, the device may further include: the MLD is also used to: configure a specific MLE to advertise mesh capabilities, wherein configuring a specific MLE includes the MLD being used to: extend a field in the MLE that indicates information shared by all links (Common Info field) by means of an element (Mesh Configuration Element) used to advertise mesh services; update a field in the MLE that indicates control over multiple links (Multi-Link Control field) by: extending a bitmap-containing subfield (PresenceBitmap subfield) in the Multi-Link Control subfield by means of an indicator (Mesh Configuration Element Presentindicator) indicating that the Mesh Configuration Element exists in the Common Info field; and further extending the PresenceBitmap subfield by means of an indicator indicating whether all links in the link have mesh capabilities.

[0045] According to the implementation of the device described in the second aspect, the device may further include: the MLD is also used to: configure a specific MLE to advertise mesh capabilities, wherein configuring a specific MLE includes: assigning a new type value in a subfield (Type subfield) of the multi-link control subfield in the MLE, the new type value indicating that the specific MLE is used for mesh operation.

[0046] According to the implementation of the device described in the second aspect, the device may further include: an MLD for updating an RNR element by including a subfield (Mesh Capable subfield) indicating that the link is available for mesh operation, wherein the value of the Mesh Capable subfield is equal to 1 to indicate that the link is available for mesh operation.

[0047] According to the implementation of the device described in the second aspect, the device may further include: the MLD is also used to: discover mesh MLOs using mesh multilink probe requests and responses, wherein the discovery includes: receiving information details of a peer mesh MLD before peering with another mesh MLD, wherein the information details received from the mesh MLD include a specific MLE with mesh capabilities, the specific MLE including a field (Link Info field) of link information about all other affiliated STAs operating in the mesh BSS or about a specific requesting affiliated STA operating in the mesh BSS.

[0048] According to the implementation of the device described in the second aspect, the device may further include: a link information field indicating which links support mesh operation and the corresponding mesh parameters.

[0049] According to the implementation of the device described in the second aspect, the device may further include: a mesh multi-link probe request including a link information field, the link information field indicating one or more specific affiliated STAs that need to respond.

[0050] According to the implementation of the device described in the second aspect, the device may further include: if all links of the MLD support mesh functionality, then the updated public information field of the MLE is used to include a mesh configuration element and indicate that all links support mesh operation, wherein the mesh information included in the mesh configuration element applies to all links; otherwise, if only some links of the MLD support mesh functionality, then information common to all mesh-enabled links of the MLD is included in the public information field of the MLD, while link-specific information is included in a sub-field (Per-STA Profile sub-element) in the link information field of the MLE indicating the STA profile, wherein the link-specific information is obtained by receiving a response to a mesh multi-link probe request from a mesh-capable peer MLD.

[0051] According to the implementation of the device described in the second aspect, the device may further include: if only some links in the MLD's links support mesh functionality, then the subfield in the Per-STA profile sub-element that indicates control over the STA (STA Control subfield) is updated to include a subfield indicating mesh parameters in the MeshCapable STA Info field and a subfield indicating mesh parameters in the Mesh Capable STA Profile field.

[0052] According to the implementation of the device described in the second aspect, the device may further include: if the value of the Mesh Capable Common subfield is equal to 0, then the value of the Mesh Capable Common subfield is set to 1, which indicates that the link supports the mesh function and that all mesh configuration information in the link-specific mesh configuration information is included in the updated MLE's STA Info subfield.

[0053] According to the implementation of the device described in the second aspect, the device may further include: if only some links in the MLD support mesh functionality, then the updated MLE includes a subfield (STAInfo subfield) indicating STA information, which includes a TBTT Adjusting subfield and / or a Mesh Power Save Level subfield.

[0054] According to the implementation of the device described in the second aspect, the device may further include: removing the TBTT adjustment subfield and / or the mesh power saving level subfield from the mesh configuration element of the public field.

[0055] According to the implementation of the device described in the second aspect, the device may further include: if the mesh profiles of each STA belonging to the corresponding mesh STA are the same, the device is further configured to: announce the mesh capability of the MLD with mesh capability by updating the predefined mesh profile elements.

[0056] According to the implementation of the device described in the second aspect, the device may further include: a predefined mesh configuration element is updated by including a subfield for mesh capability extension (Mesh CapabilityExtension subfield), the mesh configuration element including a subfield indicating mesh capability (Mesh Capability subfield), wherein the last bit of the mesh capability subfield indicates whether the mesh configuration element has been updated by the mesh capability extension subfield.

[0057] This disclosure also provides a third aspect of a mesh multi-link device (MLD) for: operating in a mesh network using multi-link operation (MLO), the mesh network including multiple mesh STAs and mesh MLDs, communicating via multiple WLAN wireless links between one or more AP MLDs and one or more non-AP MLDs, wherein each MLD has one or more affiliated STAs, each affiliated STA being used to operate on a different link specified for the mesh operation; transmitting MLO MBSS information indicating multi-link operation mesh basic service set (MLO MBSS) capabilities and / or operational parameters; wherein a specific mesh multi-link element (MLE) is included in the MLO MBSS information.

[0058] According to the implementation of the device described in the third aspect, the device may further include: an MLD for sending MLO MBSS information indicating multi-link operation mesh basic service set (MLO MBSS) capability; the MLD is also used for: sending beacon frames or non-request probe response frames; or sending probe response frames as a response to a requested probe request frame; or sending multi-link probe responses as a response to a requested multi-link probe request.

[0059] According to the implementation of the device described in the third aspect, the device may further include: an MLD for: updating reduced neighbor report (RNR) elements and announcing the updated RNR elements in beacon frames and probe response frames, and announcing specific MLEs; updating mesh operations of one or more STAs belonging to the MLD, such that the MLD can announce and discover various MBSSs on the links specified for the mesh operations.

[0060] According to the implementation of the device described in the third aspect, the device may further include: the MLD is also used to: configure a specific MLE to advertise mesh capabilities, wherein configuring a specific MLE includes the MLD being used to: extend a field in the MLE that indicates information shared by all links (Common Info field) by means of an element used to advertise mesh services (Mesh Configuration Element); update a field in the MLE that indicates control over multiple links (Multi-Link Control field) by: extending a bitmap-based subfield in the Multi-Link Control field (Presence Bitmap subfield) by means of an indicator indicating that the Mesh Configuration Element exists in the Common Info field (Mesh Configuration Element Presentindicator); and further extending the Presence Bitmap subfield by means of an indicator indicating whether all links in the link have mesh capabilities.

[0061] According to the implementation of the device described in the third aspect, the device may further include: the MLD is also used to: configure a specific MLE to advertise mesh capabilities, wherein configuring a specific MLE includes: assigning a new type value in a subfield (Type subfield) of the multi-link control subfield in the MLE, the new type value indicating that the specific MLE is used for mesh operation.

[0062] According to the implementation of the device described in the third aspect, the device may further include:

[0063] MLD is used to update RNR elements by including a subfield (MeshCapable subfield) that indicates that the link is available for mesh operations, where the value of the MeshCapable subfield is equal to 1 to indicate that the link is available for mesh operations.

[0064] According to the implementation of the device described in the third aspect, the device may further include: the MLD is also used to: discover mesh MLOs using mesh multilink probe requests and responses, wherein the discovery includes: receiving information details of a peer mesh MLD before peering with another mesh MLD, wherein the information details received from the mesh MLD include a specific MLE with mesh capabilities, the specific MLE including a field (Link Info field) of link information about all other affiliated STAs operating in the mesh BSS or about a specific requesting affiliated STA operating in the mesh BSS.

[0065] According to the implementation of the device described in the third aspect, the device may further include: the link information field, indicating which links support mesh operation and the corresponding mesh parameters.

[0066] According to the implementation of the device described in the third aspect, the device may further include: a mesh multi-link probe request including a link information field, the link information field indicating one or more specific affiliated STAs that need to respond.

[0067] According to the implementation of the device described in the third aspect, the device may further include: if all links of the MLD support mesh functionality, the updated public information field of the MLE is used to include a mesh configuration element and indicate that all links support mesh operation, wherein the mesh information included in the mesh configuration element applies to all links; otherwise, if only some links of the MLD support mesh functionality, information common to all mesh-enabled links of the MLD is included in the public information field of the MLD, while link-specific information is included in a sub-field (Per-STA Profile sub-element) in the link information field of the MLE indicating the STA profile, wherein the link-specific information is obtained by receiving a response to a mesh multi-link probe request from a peer MLD with mesh capability.

[0068] According to the implementation of the device described in the third aspect, the device may further include: if only some links in the MLD support mesh functionality, then the subfield in the Per-STA profile sub-element that indicates control over the STA (STA Control subfield) is updated to include a subfield indicating mesh parameters in the MeshCapable STA Info field and a subfield indicating mesh parameters in the Mesh Capable STA Profile field.

[0069] According to the implementation of the device described in the third aspect, the device may further include: if the value of the Mesh Capable Common subfield is equal to 0, then the Mesh Capable Common subfield is set to 1, which indicates that the link supports the mesh function and all mesh configuration information in the link-specific mesh configuration information is included in the updated STA Info subfield of the MLE.

[0070] According to the implementation of the device described in the third aspect, the device may further include: if only some links in the MLD support mesh functionality, then the updated MLE contains a subfield indicating STA information (STAInfo subfield), the subfield including a TBTT Adjusting subfield and / or a Mesh Power Save Level subfield.

[0071] According to the device implementation described in the third aspect, the device may further include: removing the TBTT adjustment subfield and / or the mesh power saving level subfield from the mesh configuration element of the public field.

[0072] According to the implementation of the device described in the third aspect, the device may further include: if the mesh profiles of each STA belonging to the corresponding mesh STA are the same, the device is further configured to: announce the mesh capability of the MLD with mesh capability by updating the predefined mesh profile elements.

[0073] According to the implementation of the device described in the third aspect, the device may further include: a predefined mesh configuration element is updated by including a subfield for mesh capability extension (Mesh CapabilityExtension subfield), the mesh configuration element including a subfield indicating mesh capability (Mesh Capability subfield), wherein the last bit of the mesh capability subfield indicates whether the mesh configuration element is updated by the mesh capability extension subfield.

[0074] This disclosure also provides a fourth aspect of a computer program product, the computer program product including program code, which, when executed on a computer or processor, performs the method according to the first aspect.

[0075] This disclosure also provides a fifth aspect of a non-transitory computer-readable medium carrying program code that, when executed by a computer device, causes the computer device to perform the method according to the first aspect. Attached Figure Description

[0076] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0077] Figure 1 The MBSS findings are illustrated schematically.

[0078] Figure 2 The following is an example of MBSS operation illustrated.

[0079] Figure 3 This illustrates a known mesh network architecture.

[0080] Figure 4 This shows a multi-link device.

[0081] Figure 5 This illustrates the MLD mesh network architecture provided in this disclosure.

[0082] Figure 6 This shows the format of the multi-link element.

[0083] Figure 7 It shows Figure 6 The format of the multi-link control field in MLE.

[0084] Figure 8 It shows Figure 6 The basic MLE format is the Per-STA configuration file sub-element format.

[0085] Figure 9 This shows the mesh configuration element format.

[0086] Figure 10 This shows the format of the mesh capability field.

[0087] Figure 11 This illustrates the updated existence bitmap subfield format of the multi-link control field provided in an embodiment of this disclosure.

[0088] Figure 12 This illustrates an updated public information field format for an MLE provided in another embodiment of this disclosure.

[0089] Figure 13 This illustrates the updated MLD parameter subfield format of the RNR element provided in an embodiment of this disclosure.

[0090] Figure 14This illustrates passive and active scanning of MBSS using a basic MLE, as provided in embodiments of this disclosure.

[0091] Figure 15 This illustrates passive and active scanning of MBSS using a mesh MLE, as provided in another embodiment of this disclosure.

[0092] Figure 16 This illustrates mesh multilink detection using mesh MLE for mesh MLO discovery, according to another embodiment of this disclosure.

[0093] Figure 17 This illustrates an updated STA control field format for a basic MLE / mesh MLE provided in another embodiment of this disclosure.

[0094] Figure 18 The STA information field format of the updated basic MLE / mesh MLE provided in this disclosure embodiment is shown.

[0095] Figure 19 This illustrates the mesh capability subfield format within a mesh configuration element provided in another embodiment of this disclosure.

[0096] Figure 20 This illustrates the mesh capability extension subfield format provided in an embodiment of this disclosure.

[0097] Figure 21 This illustrates the MLO MBSS capability advertised using an extended mesh configuration element, as provided in an embodiment of this disclosure. Detailed Implementation

[0098] Figure 1 The illustration shows several mesh STAs scanning and discovering peers. In this example, when a mesh STA (i.e., a non-AP STA that does not support Infrastructure BSS functionality) initiates a connection to the Mesh Basic Service Set (MBSS) (in other words, the mesh network), it attempts to discover other nearby mesh STAs and begins sending beacon frames advertising the MBSS. Other mesh STAs then use traditional discovery mechanisms in IEEE 802.11, such as: i) passive scanning, i.e., listening for beacon or non-request probe response frames; ii) active scanning, i.e., sending probe requests and / or receiving probe responses.

[0099] exist Figure 1 In this context, a "mesh profile" identifies the MBSS and is included in beacon frames and probe response frames. The mesh profile includes a "mesh ID," such as an information element in the management frame, used to identify an instance of the MBSS.

[0100] IEEE 802.11 defines the communication requirements for STAs operating in a mesh network. Mesh STAs discover and pair with each other to form mesh links. Data can be routed between peer mesh STAs via a series of hops through other STAs operating in the mesh network. For example, for illustration purposes, such as... Figure 2 As shown, STA O, STA A, STA B, and STA D are peers in a mesh network. These STAs can also be designated as mesh STAs. Figure 2 In this process, frames sent from STA O to destination STA D will be relayed through STA A and STA B.

[0101] For ease of explanation, Figure 3 This illustrates a typical mesh architecture that can be implemented using IEEE 802.11. Figure 3 The mesh nodes shown support the exchange of information between the mesh network and external infrastructure (e.g., BSS 1 at STA 1 or the LAN at STA 4). Here, in Figure 3 In a mesh peer-to-peer connection, the links are associated links, for example, establishing a secure connection between mesh STAs. These links typically reside in the same WLAN frequency band, such as 2.4 GHz.

[0102] IEEE 802.11be introduced multi-link devices (MLDs). For ease of explanation, Figure 4 The MLD is illustrated. The MLD communicates via multiple WLAN wireless links between the AP MLD and the non-AP MLD. This communication supports traffic exchange across multiple links and utilizes multiple channels to provide performance gains.

[0103] exist Figure 4 In the example shown, each AP MLD has one or more member APs, where each member AP operates on a different link. Similarly, each non-AP MLD has one or more member non-AP STAs, where each member non-AP STA operates on a different link. Figure 4 In the example shown, the AP MLD has three distinct links. A non-AP MLD is already associated with the AP MLD by establishing two links with it, and frames exchanged between the AP MLD and a specific non-AP MLD can be transmitted on these two links.

[0104] IEEE 802.11be also introduces dynamic link switching, where traffic can move from one link to another because a non-AP STA belonging to a non-AP MLD can be in active or power-saving mode while running on one of the links.

[0105] Figure 5 This disclosure relates to the combination of the above-described MLD concept with a mesh architecture, as provided in the embodiments of this disclosure. Figure 5 The architecture shown is Figure 3 The main difference in the mesh architecture shown is that Figure 5 The mesh MLD in the system can simultaneously use multiple links to exchange information on multiple WLAN frequency bands. Figure 5 Three mesh MLDs are shown, with 10, 20, and 30 respectively. The number of mesh MLDs is (only) three, chosen only for illustrative purposes. The architecture can include different numbers of mesh MLDs within a mesh architecture. Figure 5 The following two links are shown for mesh peering connections between mesh MLDs (e.g., mesh MLDs 10 and 20) in a mesh architecture: Link 1: 2.4 GHz Channel 1, Link 2: 5 GHz Channel 165. Figure 5 The mesh peer-to-peer connection between mesh MLDs 10 and 30 is also shown using the following three links: Link 1: 2.4 GHz Channel 1, Link 2: 5 GHz Channel 165, and Link 3: 6 GHz Channel 73. Figure 5 The mesh peer-to-peer connection between mesh MLDs 20 and 30 is also shown using the following three links: Link 1: 2.4 GHz Channel 1, Link 2: 5 GHz Channel 165.

[0106] Furthermore, IEEE 802.11 RNR elements are included in beacon frames and probe response frames, and are defined to include channel and other information about neighboring APs or APs belonging to the same AP MLD as the AP sending the beacon frame and probe response frame. This can also be referred to as a "reporting AP".

[0107] about Figure 6 A multi-link element (MLE) was introduced. The multi-link element (MLE) 100 includes information corresponding to other links in the MLD (see [link to MLD documentation]). Figure 5 An AP or non-AP STA that sends frames including MLE belongs to that MLD. For clarity, Figure 6 The format of MLE 100 is shown in the diagram. Therefore, Figure 6 The format of MLE is shown. MLE 100 (e.g., as...) Figure 6 (As shown) When exchanging data between MLDs using one of the affiliated APs / non-APs, the main components include beacon frames, probe response frames, authentication frames, association request frames, and association response frames.

[0108] Figure 6The MLE includes an element ID field (100-1), a length field (100-2), an element ID extension field (100-3), a multi-link control field (100-4), a common information field (100-5), and a link information field (100-6). The length / width of these corresponding fields (in octets) is... Figure 6 The instructions are as follows. Specifically, such as... Figure 6 As shown, MLE 100 includes a multi-link control field 100-4. In Figure 7 In the middle, it is further shown Figure 6 The Multi-Link Control field format is 100-4. Multi-Link Control field 100-4 is used to distinguish different types of MLEs, such as... Figure 7 As shown. Figure 7 The multi-link control field 100-4 includes a type subfield 100-4.1, a reserved subfield 100-4.2, and a current bitmap subfield 100-4.3. The number of bits included in each of these subfields is... Figure 7 The instructions are in accordance with the central government.

[0109] Figure 6 The MLE 100 also includes a field for transmitting information (i.e., common information) to all links. This field is called Common Information Field 100-5. Common Information Field 100-5 (see...) Figure 6 ) carries for all links (see Figure 5 Shared information.

[0110] Figure 6 The MLE 100 also includes a field that carries specific information for each link. This field is called Link Information Field 100-6, see [link information field name]. Figure 6 The link information field 100-6 of the MLE 100 carries link-specific information; see [link information]. Figure 4 The STA in the configuration file. Each of these information elements is called a Per-STA configuration file sub-element. Therefore, Figure 6 The link information field 100-6 includes a per-STA specific sub-element, namely the Per-STA profile sub-element. Link information field 100-6 carries a Per-STA profile sub-element for each member STA or link included in the MLD, for example... Figure 5 The MLD in the basic MLE 100 Per-STA configuration file has the following format: sub-elements 100-6.5. Figure 8 As shown. Therefore, Figure 8 Details of link information field 100-6 are shown. Figure 8The Per-STA configuration file sub-element 100-6 includes the sub-element ID sub-field 100-6.1, the length sub-field 100-6.2, the STA control sub-field 100-6.3, the STA information sub-field 100-6.4, and the aforementioned STA configuration file sub-field 100-6.5. Figure 8 The document provides the length / width of subfield 100-6 of the link information subfield, in octet units.

[0111] It should be noted that during the MLD discovery process, the Link Information field 100-6 is not included in the basic MLE 100-6 carried in the beacon frame and probe response frame, as described in the IEEE 802.11be amendment.

[0112] In addition, access points (APs) can send multi-link probe responses, where the AP belongs to an AP multi-link device (MLD). The probe response frame is sent in response to a multi-link probe request and carries an MLE to provide a complete or partial profile of one or more APs belonging to a specific AP MLD as defined in the IEEE 802.11be amendment.

[0113] Another element (mesh configuration element 150) is used to advertise mesh services. Mesh configuration element 150 is sent by the mesh STA in beacon frames and probe response frames. This is in Figure 9 As shown in the image.

[0114] Figure 9 The mesh configuration element 150 shown includes element ID 150-1, a length field 150-2, a field 150-3 indicating an active path selection protocol identifier, a field 150-4 indicating an active path selection metric identifier, a field 150-5 indicating a congestion control mode identifier, a field 150-6 indicating a synchronization method identifier, a field 150-7 indicating an authentication protocol identifier, a mesh formation information field 150-8, and a mesh capability field 150-9. The length / width of these fields (in octets) is... Figure 9 The instructions are as follows. Here, each subfield of the mesh configuration element identifies various protocols and methods that control the operation of the mesh network.

[0115] Specifically, mesh configuration element 150 includes mesh capability fields 150-9. Figure 10 The mesh configuration element 150 is further shown (see Figure 9 The mesh capability field is in the format 150-9. Figure 10 Each subfield in the configuration can advertise the mesh capabilities of a mesh STA; see [link to configuration]. Figure 4 and Figure 5 .

[0116] According to a first embodiment of this disclosure, a method for configuring a mesh multi-link device (MLD) is disclosed, see [link to relevant documentation]. Figure 5 This method further... Figure 14 As described in the text. Here, the MLD operates using multi-link operation (MLO) in a mesh network. The mesh network comprises multiple mesh STAs and mesh MLDs, with each MLD communicating via multiple WLAN wireless links between one or more AP MLDs and one or more non-AP MLDs. Each MLD has one or more affiliated STAs, each operating on a different link specified for the mesh operation. (See also...) Figure 14 As shown, the method includes receiving MLO MBSS information indicating multi-link operation mesh basic service set (MLO MBSS) capabilities and / or operational parameters, wherein a specific multi-link element (MLE) is included in the MLO MBSS information, and the specific MLE is used to advertise the mesh capabilities of the MLD. The RNR element includes basic information about neighboring APs to include APs belonging to the AP MLD as reporting APs. Specifically, it includes an indication of whether the belonging AP supports MBSS MLO operation.

[0117] for Figure 14 The method shown, in which receiving MLO MBSS information indicating multi-link operation mesh basic service set (MLO MBSS) capability may include: step 501, receiving a beacon frame or a non-request probe response frame; or step 503, sending a probe request frame; and step 505, receiving a probe response frame as a response to a requested probe request frame. In other words, an MLD wishing to discover MLO MBSS may: receive a beacon frame or a non-request probe response frame announcing the capability in updated basic MLE and RNR elements; or may send or broadcast a probe request frame to potential APs belonging to the peer mesh MLD, awaiting a probe response frame indicating MLO MBSS capability in updated basic MLE and RNR elements.

[0118] Therefore, modified or even new mesh MLEs can be added to each of the above options (i.e., carried in beacon frames or non-request probe response frames, or carried in probe response frames sent as a response to a requested probe request frame, or carried in mesh multilink probe responses and mesh multilink probe responses) to announce mesh capabilities, as explained in the further embodiments below. Furthermore, it should be noted that when an MLD receives a frame including MLO MBSS capabilities, it can use a peer-to-peer mesh MLD device to authenticate peers.

[0119] Therefore, the first embodiment illustrates a protocol for how MLDs discover peer-to-peer mesh MLDs.

[0120] According to another embodiment of this disclosure, such as Figure 6 As shown, MLE 100 can be updated to support the notification and discovery of MLO MBSS. Therefore, as Figure 12 As shown, the updated MLE 100' has been implemented. For Figure 12 The updated MLE 100' can Figure 9 The mesh configuration element 150 shown is added as an extension of the public information field of the basic MLE 100. Therefore, the public information field 100-5 of the basic MLE 100 is updated to public information field 100-5'. This is in Figure 12 As shown in the image. Figure 12 The updated MLE 100-5' provided in this embodiment is shown. For example... Figure 12 As shown, the existence of this additional subfield, i.e. Figure 9 Mesh configuration element 150 indicates the updated MLE 100' to announce mesh capabilities.

[0121] Figure 12 The updated MLE 100' includes... Figure 6 The same subfields 100-1, 100-2, 100-3, 100-4, and 100-6 described in the format of MLE 100. These subfields will not be repeated here. In addition, subfield 100-5 is updated. The updated subfield 100-5 of MLE 100' includes the following subfields: Common Information Length subfield 100-5.1, MLDMAC Address subfield 100-5.2, Link ID Information subfield 100-5.3, Subfield 100-5.3 indicating BSS parameter change count, Media Synchronization Delay Information subfield 100-5.5, EML Capability subfield 100-5.6, MLD Capability and Operation subfield 100-5.7, AP MLD ID subfield 100-5.8, Extended MLD Capability and Operation subfield 100-5.9, and Mesh Configuration Element 150. The length / width (in octets) of these corresponding subfields is... Figure 12 The information is provided in the text.

[0122] In this embodiment, each STA belonging to the mesh MLD (see Figure 4 and Figure 5 The updated MLE 100' can be advertised in the beacon frames and probe response frames it sends. As mentioned above, when the updated MLE 100' is used in discovery mode, for example to advertise information about the MLD, the link information field 100-6 of MLE 100 or 100' is not included in the corresponding MLE. Therefore, in order to send concise information about available MLD links suitable for mesh operation, the RNR element needs to be included in the beacon frame or probe response frame. The RNR element supports peer-to-peer mesh MLDs in determining available links and affiliated STAs for mesh peer-to-peer connections and operations. The RNR element is updated to indicate links suitable for mesh operation. Furthermore, for this embodiment, STAs that support mesh functionality, such as STAs sending beacon frames and / or probe response frames including the updated MLE 100', must belong to the mesh MLD.

[0123] like Figure 7 As shown, Figure 6 The basic MLE 100's multilink control field 100-4 includes an existence bitmap subfield 100.4.3. The existence bitmap subfield 100.4.3 of the multilink control field 100-4 also needs to be updated to become the updated existence bitmap subfield 100-4'. The purpose of updating the existence bitmap subfield 100-4.3 to become the updated existence bitmap subfield 100-4' is to indicate that the mesh configuration element 150 is added to the MLE 100's public information field 100-5, thereby producing the updated public information field 100-5' of the updated MLE 100'. For example... Figure 11 As shown, the updated presence bitmap 100-4.3' subfield of the updated multilink control field 100-4' includes a mesh configuration element presence indicator subfield 104-4.3.8. This indicator 104-4.3.8 includes a new subfield "Mesh configuration element present". When this subfield is set to 1, indicator 104-4.3.8 indicates that the updated MLE 100' includes mesh configuration element 150, see [link to MLE 100]. Figure 11 and Figure 12 The other bits of the bitmap subfield 100-4.3' are defined in the IEEE 802.11be amendment.

[0124] Another new subfield, "Support Mesh Functionality Public," is also included in the updated Existence Bitmap subfield 100-4.3', see [link / reference]. Figure 11When this subfield (i.e., "Support Mesh Functionality Public") is set to 1, it indicates that all links in this MLD support mesh functionality. In this case, all mesh configuration information required for each link in those supporting mesh functionality is included in the updated Public Information field 100-5' of MLE 100'. If the "Support Mesh Functionality Public" bit in the updated Existence Bitmap subfield 100-4.3' (see...) Figure 11 Setting it to 0 indicates that not all links in the MLD support mesh operation.

[0125] In summary, Figure 12 This illustrates updating the public information field 100-5 of MLE 100 using mesh configuration element 150 (see [link]). Figure 6 This will become the updated public information field 100-5' and the updated MLE 100'. Other public information fields of MLEs can be updated in a similar manner.

[0126] The remaining elements of public information fields 100-5 and 100-5' are described in the IEEE 802.11be amendment. Some information within mesh configuration element 150 may not be shared by all links within the MLD. This is further considered in Example 5.

[0127] In addition, Figure 12 In the example shown, the mesh configuration element 150 is located at the end of the updated public information field 100-5'. This is merely an example; the mesh configuration element 150 can be placed in other positions within the updated public information field 100-5'. It should be noted that the length of the mesh configuration element 150 is 9 octets or 10 octets, for example, the length updated as in Example 6.

[0128] Regarding the RNR element, the RNR element includes the simplified parameter set of each AP belonging to the other APs in the AP MLD as the reporting AP. Figure 13 This illustrates that, in order to indicate a link that can be used for mesh operation, one of two bits is used within the reserved subfield 160 of the MLD parameter subfield within the RNR.

[0129] Figure 13 The RNR MLD parameter subfield 160 is shown to include the AP MLD ID subfield 160-1, Link ID subfield 160-2, BSS parameter change count subfield 160-3, "Include all updates" subfield 160-4, "Disable link indication" subfield 160-5, Support mesh functionality subfield 160-6, and Reserved subfield 160-7.

[0130] like Figure 13As shown, the reserved subfield of RNR MLD parameter subfield 60 is split, with the first subfield named "Support Mesh Functionality" and set to 1 to indicate that the link is available for mesh operation.

[0131] Figure 14 An exemplary messaging flow is shown for using an updated MLE to announce and discover MLO MBSS capabilities. Figure 14 The first embodiment of this disclosure illustrates passive and active scanning of MBSS using a basic MLE.

[0132] exist Figure 14 In this example, mesh MLD2, labeled with reference numeral 20, sends an updated MLE (e.g., updated MLE 100') from a beacon frame or non-request probe response frame to mesh MLD1, labeled with reference numeral 10. The RNR element includes information about each STA belonging to the mesh MLD STA. Alternatively, if mesh MLD2 receives a conventional probe request from MLD1, it can use this opportunity to add updated MLE and RNR elements to the probe response frame, i.e., in addition to the conventional probe response information.

[0133] It should be noted that Multi-Link Operation (MLO) defines multi-link probe requests and multi-link probe responses as probe request frames with probe request MLE and probe response frames with basic MLE 100.

[0134] Multi-link probe requests and responses are the ability of non-AP MLDs to discover individual AP MLDs.

[0135] In summary, Example 2 enables the mesh MLD to announce its MLO MBSS capability in the updated MLE 100'.

[0136] While Embodiment 2 involves updating MLE 100 to become the updated MLE 100', this disclosure discloses another embodiment. The message flow of Embodiment 3 is as follows: Figure 15 As shown. For Example 3, it is not an update (basic) MLE 100 (i.e., an update). Figure 6 As shown in MLE 100, Example 3 involves defining a new mesh MLE. In a sense, this can be considered a “complete” update of MLE 100. Figure 7 The multi-link control field is shown. Example 3 uses this multi-link control field 100-4 and introduces and assigns a new "type" within it; see [link to example]. Figure 7The multi-link control field 100-4-4 is shown as a type subfield 100-4.1. An example value "5" can be assigned to this type value to indicate that the new MLE of Embodiment 3 is used for mesh operation. It should be noted that the value "5" can be replaced by different appropriate values. A new type, "5," has been defined for the type subfield 100-4.1 within the multi-link control field 100-4, and the operation and behavior of the mesh MLE are otherwise identical to the updated MLE 100 described above.

[0137] Figure 15 An exemplary message flow for announcing and discovering MLO MBSS capabilities using the mesh MLE of Embodiment 3 is shown. Figure 15 The present disclosure illustrates passive and active scanning of MBSS using a (novel) mesh MLE, as provided in Embodiment 3.

[0138] exist Figure 15 In step 601, mesh MLD2 (element 20) sends a mesh MLE within a beacon frame or non-request probe response frame to mesh MLD1 (element 10). The RNR element includes information about each STA belonging to the mesh MLD STA. Steps 603 and 605 are respectively related to... Figure 14 Steps 503 and 505 are similar.

[0139] Or, if Figure 15 If a mesh MLD2 receives a conventional probe request from a STA belonging to MLD1, it can take this opportunity to include mesh MLE and RNR elements in the probe response frame, that is, in addition to the conventional probe response information.

[0140] It should be noted that, Figure 14 and Figure 15 They describe the same frame sequence, but with the following differences: Figure 14 Includes the option to use an updated / modified base MLE to include indications of MBSS MLO capabilities and parameters. Figure 15 Includes the option to use (new) mesh MLE to include indications of MBSS MLO capabilities and parameters.

[0141] In summary, Example 3 enables the mesh MLD to advertise its MLO MBSS capability in the new mesh MLE. Otherwise, Example 3 is similar to Example 2.

[0142] Figure 16Another embodiment of this disclosure relates to this embodiment. According to embodiment 4, a mesh MLD can use a mesh multi-link (ML) probe request sent to a peer MLD to receive complete information details of the peer mesh MLD before the mesh peer connection is established. Therefore, according to this embodiment, this enables the MLD to probe the peer MLD in a different manner to obtain more information. The mesh multi-link probe request is a probe request frame that includes a mesh MLE.

[0143] According to this embodiment, the peer-to-peer mesh MLD will respond with a mesh multi-link probe response, which includes a mesh MLE. The mesh MLE includes a link information subfield of full-link information (i.e., the mesh parameters of those links) on all other member STAs operating in the mesh BSS or on the member STA of the specific request operating in the mesh BSS. Furthermore, according to this embodiment, the link information subfield indicates which links are available for negotiation in the mesh peer-to-peer connection. Additionally, the mesh multi-link probe request may include a link information portion to indicate the required response for each specific member STA. Figure 16 An exemplary message flow of this embodiment is shown.

[0144] In summary, this embodiment supports the use of mesh multilink probe requests and responses within a mesh MLE to announce MLOMBSS capabilities.

[0145] Figure 17 Another embodiment of this disclosure is involved. This embodiment relates to links existing in MLD. all When all links support mesh functionality, and sometimes in MLD... Only one subset of links If mesh functionality is supported, then it can be used. Figure 12 The updated MLE 100's basic MLE100 public information field 100-5 (see the updated MLE 100'). Figure 6 Or, in Example 3, the new MLE's public information fields 100-5 may be used to include mesh configuration elements 150, as described in conjunction with Example 2 (see Example 2). Figure 12 (and as described in conjunction with Embodiment 3.) The mesh information included in mesh configuration element 150 is then applied to all links.

[0146] On the other hand, in another scenario where only some links support mesh functionality, the common information field 100-5 of the MLE 100 may not be applicable to all information related to the mesh configuration element 150. In this case, the mesh configuration element 150 needs to be split so that common information about the mesh network remains in the common information field (e.g., 100-5 or 100-5'), while link-specific information is moved to the Per-STA configuration sub-element 100-6.5 of the link information field 100-6 of the MLE 100, such as... Figure 8 The first one shown is shown in the middle.

[0147] It should be noted that since the link information field 100-6 is not transmitted in the beacon, this information must be obtained from the peer mesh MLD using a mesh multilink probe request.

[0148] To indicate the presence of mesh configuration information in the Per-STA configuration file sub-element 100-6.5, the STA control field 100-6.3 (see...) Figure 8 ) has also been updated, such as Figure 17 As shown. Therefore, Figure 8 The STA control field 100-6.3 in the original text has been changed to the updated STA control field 100-6.3' of the updated link information subfield 100-6'. The newly assigned subfield also describes where the link-specific information will be found.

[0149] like Figure 17 As shown, the updated STA control field 100-6.3' in the updated link information subfield 100-6' includes: link ID subfield 100-6.3.1, "Complete Configuration File" subfield 100-6.3.2, "STA MAC Address Exists" subfield 100-6-3.3, "Beacon Interval Exists" subfield 100-6.3.4, TSF Offset Exists subfield 100-6.3.5, DTIM Information Exists subfield 100-6.3.6, NSTR Link Pair Exists subfield 100-6.3.7, NSTR Bitmap Size subfield 100-6.3.8, "BSS Parameter Change Count Exists" subfield 100-6.3.9, STA Information Supporting Mesh Functionality subfield 100-6.3.10', STA Configuration File Supporting Mesh Functionality subfield 100-6.3.11', and reserved subfield 100-6.3.12.

[0150] Therefore, as Figure 17As shown, the reserved bits at the end of the STA control field 100-6.3' are used to indicate whether the link supports mesh functionality. The STA information subfield 100-6-3.10' and the STA configuration subfield 100-6.3.11' supporting mesh functionality are mutually exclusive; the values ​​of the two subfields (bits) cannot be set to 1 simultaneously.

[0151] In this embodiment, if the "Support Mesh Functionality Common" bit (i.e., the subfield "Support Mesh Functionality Common" in the updated existence bitmap subfield 100-4.3', see...) Figure 11 If ) equals 0, then mesh functionality is supported. When STA information bit 100-6-3.10' is set to 1, it indicates that the link supports mesh functionality, and all mesh configuration information in the link-specific mesh configuration information is included in the STA information field 100-6.4 of the updated link information subfield 100-6'.

[0152] In this embodiment, Figure 18 An example is shown where the link-specific subfield of mesh configuration element 150 is placed in the STA information field (i.e., the updated STA information field 100-6.4'). Figure 18 In the updated STA information field 100-6.4', the following subfields are included: STA information length subfield 100-6.4.1, STA MAC address subfield 100-6.4.2, beacon interval subfield 100-6.4.3, TSF offset subfield 100-6.4.4, DTIM information subfield 100-6.4.5, NSTR indicator bitmap subfield 100-6.4.6, BSS parameter change count existence subfield 100-6.4.7, TBTT adjustment subfield 100-6.4.8', mesh power saving level subfield 100-6.4.9', and reserved subfield 100-6.4.10'. It should be noted that... Figure 17 and Figure 18 The (sub)fields with the same name are identical, but they are derived from 100-6.3' or 100-6.4' respectively, so different figure labels are used to indicate this difference.

[0153] The "TBTT Adjustment" and "Mesh Power Saving Level" subfields of the mesh configuration element are therefore moved to the STA information field 100-6.4' of the updated link information subfield 100-6'', because these parameters are link-specific. These subfields should be removed from the mesh configuration element 150 within the common field 100-5', see [link to relevant documentation]. Figure 12 .

[0154] Additionally, if the "Support Mesh Functionality Public" bit (i.e., the subfield "Support Mesh Functionality Public" in the updated existence bitmap subfield 100-4.3', see...) Figure 11 If 0 is equal to 0, then mesh functionality is supported. When bit 100-6.3.11' in the STA profile is set to 1, it indicates that the link supports mesh functionality, and all mesh configuration information in the link-specific mesh configuration information is included in the STA profile field.

[0155] According to IEEE 802.11be D4.0, such as Figure 8 , Figure 17 and Figure 18 The specific format of subfield 100-6.5 in the STA configuration file shown is highly dependent on the context in which it is used.

[0156] Similarly, when comparing Figure 10 and Figure 18 At that time, the subfield "TBTT Adjustment" 150-9.6 becomes subfield 100-6.4.8', and the subfield "Mesh Power Saving Level" 150-9.7 becomes 100-6.4.9'. That is, these subfields are moved from the mesh configuration element 150 to the end of the STA configuration file field 100-6.5 because these parameters are link-specific. In other words, the two subfields "TBTT Adjustment" 100-6.4.8' and "Mesh Power Saving Level" 100-6.4.9' can be added to the "STA Information" field 100-6.4' (see...). Figure 17 ) or "STA Profile" field 100-6.5 (e.g. Figure 18 (as shown) at the end.

[0157] Therefore, Example 5 enables the traditional mesh configuration information in the mesh configuration elements to be remapped into the MLD architecture, thereby providing common MLD mesh-specific information and MLD mesh link-specific information.

[0158] Figure 19 and Figure 20 Another embodiment of this disclosure relates to embodiment 6. According to embodiment 6, an alternative method for notifying a mesh MLD is provided. According to embodiment 6, the mesh MLD is notified by updating known mesh configuration elements, such as mesh configuration elements according to the IEEE 802.11 standard. In other words, notifying a mesh MLD may include reusing elements such as… Figure 3 The STA is shown with traditional mesh signaling, but slightly enhanced. This is only possible if the mesh profile of each STA belonging to the mesh STA MLD is the same.

[0159] Figure 19 The updated mesh configuration element 150' is shown.

[0160] Elements 150-1, 150-2, ..., 150-9 have already been... Figure 10 As previously mentioned, I will not repeat myself here. Figure 19 The updated mesh configuration element also includes elements 150-10' of the mesh capability extension field, referred to as updated mesh configuration element 150'. Here, a reserved subfield is allocated in the mesh capability extension field 150-10' to announce mesh MLO capabilities. The enhanced mesh configuration element 150' is then sent in beacon frames and probe response frames. Information about links is then requested using multi-link probe requests and responses as described in Embodiment 4.

[0161] In addition, bit 7 of the mesh capability subfield 150-9 of mesh configuration element 150' indicates that there is an additional subfield "mesh capability extension" 150-10' at the end of mesh configuration element 150'.

[0162] Figure 20 The subfield of the mesh capability extension subfield 150-10' is shown. Figure 20 The diagram shows the Mesh Capability Extension subfield 150-10', which includes the CT M-AP Enable subfield 150-10.1', the Mesh MLO Enable subfield 150-10.2', and the Reserved subfield 150-10.3'. This subfield... Figure 20 The text indicates that the mesh MLO enabled subfield 150-10.2' is used.

[0163] Figure 21 An example message stream is shown. Figure 21 This illustrates mesh MLD 2 (i.e., element 20) transmitting a beacon including an updated mesh configuration unit 150' (step 801). The beacon frame is a broadcast frame. Figure 21 As shown, the beacon frame is received by all (nearby) receivers, including Mesh MLD-1 and element 10. Alternatively, Mesh MLD-1 (i.e., element 10) sends a probe request frame to Mesh MLD 2 (element 20) (step 803). Mesh MLD 2 then responds by sending a probe response frame including the updated mesh configuration element 150' (step 805).

[0164] Therefore, in Embodiment 6, the conventional mesh configuration element 150 is updated to mesh configuration element 150', which is capable of announcing MLO MBSS capabilities.

[0165] Overview

[0166] In summary, the key points of this disclosure are as follows:

[0167] This disclosure provides a protocol for how an MLD discovers peer-to-peer mesh MLDs.

[0168] This disclosure provides new subfield definitions to enable mesh MLDs to advertise their MLO MBSS capabilities.

[0169] Furthermore, this disclosure modifies the existing IEEE 802.11 mesh STA signaling to enable mesh MLDs to advertise their MLO MBSS capabilities.

[0170] Abbreviations

[0171] AP Access Point

[0172] BSS Basic Service Set

[0173] DS / LAN Distributed System / Local Area Network

[0174] DTIM Delivery Traffic Indication Map

[0175] LAN (Local Area Network)

[0176] MAC Media Access Control

[0177] MBSS Mesh Basic Service Set

[0178] MBCA (Mesh Beacon Collision Avoidance)

[0179] MCF Mesh Coordination Function

[0180] MCCA (MCF Controlled Channel Access)

[0181] ML Multi-Link

[0182] MLD (Multi-Link Device)

[0183] MLE (Multi-Link Element)

[0184] MLO (Multi-Link Operation)

[0185] MLO MBSS (Multi-Link Operation MBSS)

[0186] NSTR Number of Streams

[0187] RNR Reduced Neighbor Report

[0188] STA Station

[0189] TBTT (Target Beacon Transmission Time)

[0190] TSF Timing Synchronization Function

[0191] WLAN (Wireless Local Area Network)

Claims

1. A method for configuring a mesh multi-link device (MLD), characterized in that, The MLD operates using Multi-Link Operation (MLO) in a mesh network comprising multiple mesh STAs and mesh MLDs. Each MLD communicates via multiple WLAN wireless links between one or more AP MLDs and one or more non-AP MLDs. Each MLD has one or more affiliated STAs, and each affiliated STA operates on a different link specified for mesh operation. The method includes: Receive MLO MBSS information indicating the multilink operation mesh basic service set (MLO MBSS) capabilities and / or operation parameters; The specific mesh multilink element (MLE) is included in the MLO MBSS information. The specific MLE is used to announce the mesh capability of the MLD.

2. The method according to claim 1, characterized in that, The received MLO MBSS information indicating the Multilink Operation Mesh Basic Service Set (MLO MBSS) capability includes: Receive beacon frames or non-request probe response frames; or Receive a probe response frame as a response to the requested probe request frame; or Receive multilink probe responses as a response to the requested multilink probe request.

3. The method according to claim 1 or 2, characterized in that, Also includes: Update the Simplified Neighbor Report (RNR) element and announce the updated RNR element in the beacon frame and probe response frame, and announce the specific MLE; The mesh operation of one or more STAs belonging to the MLD is updated so that the MLD can advertise and discover various MBSSs on the links specified for the mesh operation.

4. The method according to any one of claims 1 to 3, characterized in that, Also includes: Configure the specific MLE to advertise the mesh capability, wherein configuring the specific MLE includes: The MLE is expanded with a field (public information field) that indicates information shared by all links by an element used to announce mesh services (mesh configuration element). The MLE field indicating control over multiple links (multi-link control field) is updated by: extending the bitmap subfield of the multi-link control subfield (existence bitmap subfield) with an indicator indicating the existence of the mesh configuration element in the public information field (mesh configuration element existence indicator); and further extending the existence bitmap subfield with an indicator indicating whether all links in the link have the mesh capability.

5. The method according to claim 2 or 3, characterized in that, Also includes: Configure the specific MLE to advertise the mesh capability, wherein configuring the specific MLE includes: In the MLE, in the subfield indicating control of multiple links (multi-link control subfield), a new type value is assigned in the subfield of the multi-link control subfield (type subfield), the new type value indicating that the specific MLE is used for the mesh operation.

6. The method according to claim 4 or 5, which is dependent on claim 3, is characterized in that, The method further includes: The RNR element is updated by including a subfield (support mesh functionality subfield) that indicates that the link is available for the mesh operation, wherein the value of the support mesh functionality subfield is equal to 1, indicating that the link is available for the mesh operation.

7. The method according to any one of the preceding claims, characterized in that, Also includes: Mesh MLOs are discovered using mesh multilink probe requests and responses, wherein the discovery includes: receiving information details of the peer mesh MLO before establishing a peer connection with another mesh MLO. The information details received from the mesh MLD include the specific MLE having the mesh capability, and the specific MLE includes a field (link information field) of link information corresponding to all other subordinate STAs operating in the mesh BSS or relating to a specific request of a subordinate STA operating in the mesh BSS.

8. The method according to claim 7, characterized in that, The link information field indicates which links support the mesh operation and the corresponding mesh parameters.

9. The method according to claim 7 or 8, characterized in that, The mesh multi-link probe request includes the link information field, which indicates one or more specific affiliated STAs that need to respond.

10. The method according to any one of claims 4 to 7, characterized in that, If all links of the MLD support mesh functionality, the updated MLE's public information field is used to include the mesh configuration element and indicate that all links support the mesh operation, wherein the mesh information included in the mesh configuration element applies to all links; otherwise, If only some links in the MLD support mesh functionality, the information shared by all mesh-enabled links of the MLD is included in the common information field of the MLD, while the link-specific information is included in the link information field of the MLE in a subfield (Per-STA profile sub-element) indicating the STA profile, wherein the link-specific information is obtained by receiving a response to a mesh multi-link probe request from a peer MLD with mesh capabilities.

11. The method according to claim 10, characterized in that, If only some links in the MLD support mesh functionality, the subfield in the Per-STA profile sub-element that indicates control over the STA (STA control subfield) is updated to include a subfield indicating mesh parameters in the STA information field that supports mesh functionality and a subfield indicating mesh parameters in the STA profile field that supports mesh functionality.

12. The method according to claim 11, characterized in that, If the value of the Support Mesh Functionality public subfield is equal to 0, then the value of the Support Mesh Functionality STA Information subfield is equal to 1. This indicates that the link supports mesh functionality and that all mesh configuration information in the link-specific mesh configuration information is included in the STA Information subfield of the updated MLE.

13. The method according to claims 10 to 12, characterized in that, If only some links in the MLD support mesh functionality, the subfield indicating STA information (STA information subfield) in the updated MLE includes the TBTT adjustment subfield and / or the mesh power saving level subfield.

14. The method according to claim 13, characterized in that, The TBTT adjustment subfield and / or the mesh power saving level subfield are removed from the mesh configuration element of the common subfield.

15. The method according to any one of claims 1 to 3, characterized in that, If the mesh configuration files of each STA belonging to the corresponding mesh STA are the same, then the method further includes: The mesh capability of the MLD with the mesh capability is announced by updating the predefined mesh configuration element.

16. The method according to claim 15, characterized in that, The predefined mesh configuration element is updated by including a subfield for mesh capability extension (mesh capability extension subfield). The mesh configuration element includes a subfield indicating the mesh capability (mesh capability subfield), wherein the last bit of the mesh capability subfield indicates whether the mesh configuration element has been updated by the mesh capability extension subfield.

17. A mesh multi-link device (MLD), characterized in that, The MLD is used for: Multi-link operation (MLO) is used in a mesh network comprising multiple mesh STAs and mesh MLDs. Communication is achieved through multiple WLAN wireless links between one or more AP MLDs and one or more non-AP MLDs, wherein each MLD has one or more affiliated STAs, and each affiliated STA is used to operate on a different link specified for mesh operation; Receive MLO MBSS information indicating the multilink operation mesh basic service set (MLO MBSS) capabilities and / or operation parameters; The specific mesh multilink element (MLE) is included in the MLO MBSS information. The specific MLE is used to announce the mesh capability of the MLD.

18. The device according to claim 17, characterized in that, The MLD is used to receive MLO MBSS information indicating the capabilities of the Multi-Link Operational Mesh Basic Service Set (MLO MBSS). The MLD is also used for: Receive beacon frames or non-request probe response frames; or Receive a probe response frame as a response to the requested probe request frame; or Receive multilink probe responses as a response to the requested multilink probe request.

19. The device according to claim 17 or 18, characterized in that, The MLD is also included for: Update the Simplified Neighbor Report (RNR) element and announce the updated RNR element in the beacon frame and probe response frame, and announce the specific MLE; The mesh operation of one or more STAs belonging to the MLD is updated so that the MLD can advertise and discover various MBSSs on the links specified for the mesh operation.

20. The device according to any one of claims 17 to 19, characterized in that, The MLD is also used for: Configure the specific MLE to advertise the mesh capability, wherein configuring the specific MLE includes the MLD for: The MLE is expanded with a field (public information field) that indicates information shared by all links by an element used to announce mesh services (mesh configuration element). The MLE field indicating control over multiple links (multi-link control field) is updated by: extending the bitmap subfield of the multi-link control subfield (existence bitmap subfield) with an indicator indicating the existence of the mesh configuration element in the public information field (mesh configuration element existence indicator); and further extending the existence bitmap subfield with an indicator indicating whether all links in the link have the mesh capability.

21. The device according to claim 17 or 18, characterized in that, The MLD is also used for: Configure the specific MLE to advertise the mesh capability, wherein configuring the specific MLE includes: In the MLE, in the subfield indicating control of multiple links (multi-link control subfield), a new type value is assigned in the subfield of the multi-link control subfield (type subfield), the new type value indicating that the specific MLE is used for the mesh operation.

22. The device according to claim 20 or 21, which is dependent on claim 19, is characterized in that, The device also includes: The MLD is used to update the RNR element by including a subfield (support mesh functionality subfield) that indicates that the link is available for the mesh operation, wherein the value of the support mesh functionality subfield is equal to 1, indicating that the link is available for the mesh operation.

23. The device according to any one of the preceding claims, characterized in that, The MLD is also used for: Mesh MLOs are discovered using mesh multilink probe requests and responses, wherein the discovery includes: receiving information details of the peer mesh MLO before establishing a peer connection with another mesh MLO. The information details received from the mesh MLD include the specific MLE having the mesh capability, and the specific MLE includes a field (link information field) about all other affiliated STAs operating in the mesh BSS or about the affiliated STA of a specific request operating in the mesh BSS.

24. The device according to claim 23, characterized in that, The link information field indicates which links support the mesh operation and the corresponding mesh parameters.

25. The device according to claim 23 or 24, characterized in that, The mesh multi-link probe request includes the link information field, which indicates one or more specific affiliated STAs that need to respond.

26. The device according to any one of claims 20 to 23, characterized in that, If all links of the MLD support mesh functionality, the updated MLE's public information field is used to include the mesh configuration element and indicate that all links support the mesh operation, wherein the mesh information included in the mesh configuration element applies to all links; otherwise, If only some links in the MLD support mesh functionality, the information shared by all mesh-enabled links of the MLD is included in the common information field of the MLD, while link-specific information is included in the link information field of the MLE in a subfield (Per-STA profile sub-element) indicating the STA profile, wherein the link-specific information is obtained by receiving a response to a mesh multi-link probe request from a peer MLD with mesh capabilities.

27. The device according to claim 26, characterized in that, If only some links in the MLD support mesh functionality, the subfield in the Per-STA profile sub-element that indicates control over the STA (STA control subfield) is updated to include a subfield indicating mesh parameters in the STA information field that supports mesh functionality and a subfield indicating mesh parameters in the STA profile field that supports mesh functionality.

28. The device according to claim 27, characterized in that, If the value of the Support Mesh Functionality public subfield is equal to 0, then the value of the Support Mesh Functionality STA Information subfield is set to 1. This indicates that the link supports mesh functionality and that all mesh configuration information in the link-specific mesh configuration information is included in the STA Information subfield of the updated MLE.

29. The device according to claims 26 to 28, characterized in that, If only some links in the MLD support mesh functionality, the subfield indicating STA information (STA information subfield) in the updated MLE includes the TBTT adjustment subfield and / or the mesh power saving level subfield.

30. The device according to claim 29, characterized in that, The TBTT adjustment subfield and / or the mesh power saving level subfield are removed from the mesh configuration element of the public field.

31. The device according to any one of claims 17 to 19, characterized in that, If the mesh profiles of each STA belonging to the corresponding mesh STA are the same, the device is also used for: The mesh capability of the MLD with the mesh capability is announced by updating the predefined mesh configuration element.

32. The device according to claim 31, characterized in that: The predefined mesh configuration element is updated by including a subfield for mesh capability extension (mesh capability extension subfield). The mesh configuration element includes a subfield indicating the mesh capability (mesh capability subfield), wherein the last bit of the mesh capability subfield indicates whether the mesh configuration element has been updated by the mesh capability extension subfield.

33. A mesh multi-link device (MLD), characterized in that, The MLD is used for: Multi-link operation (MLO) is used in a mesh network comprising multiple mesh STAs and mesh MLDs. Communication is achieved through multiple WLAN wireless links between one or more AP MLDs and one or more non-AP MLDs, wherein each MLD has one or more affiliated STAs, and each affiliated STA is used to operate on a different link specified for mesh operation; Send MLO MBSS information indicating the multi-link operation mesh basic service set (MLO MBSS) capabilities and / or operation parameters; The specific mesh multilink element (MLE) is included in the MLO MBSS information.

34. The device according to claim 33, characterized in that, The MLD is used to send MLO MBSS information indicating the capabilities of the Multi-Link Operational Mesh Basic Service Set (MLO MBSS). The MLD is also used for: Send a beacon frame or a non-request probe response frame; or Send a probe response frame as a response to the requested probe request frame; or Send a multilink probe response as a response to the requested multilink probe request.

35. The device according to claim 33 or 34, characterized in that, The MLD is also included for: Update the Simplified Neighbor Report (RNR) element and announce the updated RNR element in the beacon frame and probe response frame, and announce the specific MLE; The mesh operation of one or more STAs belonging to the MLD is updated so that the MLD can advertise and discover various MBSSs on the links specified for the mesh operation.

36. The device according to any one of claims 33 to 35, characterized in that, The MLD is also used for: Configure the specific MLE to advertise the mesh capability, wherein configuring the specific MLE includes the MLD for: The MLE is expanded with a field (public information field) that indicates information shared by all links by an element used to announce mesh services (mesh configuration element). The MLE field indicating control over multiple links (multi-link control field) is updated by: extending the bitmap subfield (existence bitmap subfield) of the multi-link control field with an indicator indicating that the mesh configuration element exists in the public information field (mesh configuration element existence indicator); and further extending the existence bitmap subfield with an indicator indicating whether all links in the link have the mesh capability.

37. The device according to claim 33 or 34, characterized in that, The MLD is also used for: Configure the specific MLE to advertise the mesh capability, wherein configuring the specific MLE includes: In the MLE, in the subfield indicating control of multiple links (multi-link control subfield), a new type value is assigned in the subfield of the multi-link control subfield (type subfield), the new type value indicating that the specific MLE is used for the mesh operation.

38. The device according to claim 36 or 37, which is dependent on claim 19, characterized in that, The device also includes: The MLD is used to update the RNR element by including a subfield (support mesh functionality subfield) that indicates that the link is available for the mesh operation, wherein the value of the support mesh functionality subfield is equal to 1, indicating that the link is available for the mesh operation.

39. The device according to any one of the preceding claims, characterized in that, The MLD is also used for: Mesh MLOs are discovered using mesh multilink probe requests and responses, wherein the discovery includes: receiving information details of the peer mesh MLO before establishing a peer connection with another mesh MLO. The information details received from the mesh MLD include the specific MLE having the mesh capability, and the specific MLE includes a field (link information field) about all other affiliated STAs operating in the mesh BSS or about the affiliated STA of a specific request operating in the mesh BSS.

40. The device according to claim 39, characterized in that, The link information field indicates which links support the mesh operation and the corresponding mesh parameters.

41. The device according to claim 39 or 40, characterized in that, The mesh multi-link probe request includes the link information field, which indicates one or more specific affiliated STAs that need to respond.

42. The device according to any one of claims 36 to 39, characterized in that, If all links of the MLD support mesh functionality, the updated MLE's public information field is used to include the mesh configuration element and indicate that all links support the mesh operation, wherein the mesh information included in the mesh configuration element applies to all links; otherwise, If only some links in the MLD support mesh functionality, the information shared by all mesh-enabled links of the MLD is included in the common information field of the MLD, while link-specific information is included in the link information field of the MLE in a subfield (Per-STA profile sub-element) indicating the STA profile, wherein the link-specific information is obtained by receiving a response to a mesh multi-link probe request from a peer MLD with mesh capabilities.

43. The device according to claim 42, characterized in that, If only some links in the MLD support mesh functionality, the subfield in the Per-STA profile sub-element that indicates control over the STA (STA control subfield) is updated to include a subfield indicating mesh parameters in the STA information field that supports mesh functionality and a subfield indicating mesh parameters in the STA profile field that supports mesh functionality.

44. The device according to claim 43, characterized in that, If the value of the Support Mesh Functionality public field is equal to 0, the Support Mesh Functionality STA Information subfield is set to 1. This indicates that the link supports mesh functionality and that all mesh configuration information in the link-specific mesh configuration information is included in the STA Information subfield of the updated MLE.

45. The device according to claims 42 to 44, characterized in that, If only some links in the MLD support mesh functionality, the subfield indicating STA information (STA information subfield) in the updated MLE includes the TBTT adjustment subfield and / or the mesh power saving level subfield.

46. ​​The device according to claim 45, characterized in that, The TBTT adjustment subfield and / or the mesh power saving level subfield are removed from the mesh configuration element of the public field.

47. The device according to any one of claims 33 to 35, characterized in that, If the mesh profiles of each STA belonging to the corresponding mesh STA are the same, the device is further configured to: The mesh capability of the MLD with the mesh capability is announced by updating the predefined mesh configuration element.

48. The device according to claim 47, characterized in that: The predefined mesh configuration element is updated by including a subfield for mesh capability extension (mesh capability extension subfield). The mesh configuration element includes a subfield indicating the mesh capability (mesh capability subfield), wherein the last bit of the mesh capability subfield indicates whether the mesh configuration element has been updated by the mesh capability extension subfield.

49. A computer program product including program code, characterized in that, When the program code is executed on a computer or processor, it is used to perform the method according to any one of claims 1 to 16.

50. A non-transitory computer-readable medium carrying program code, characterized in that, When the computer device executes the program code, it causes the computer device to perform the method according to any one of claims 1 to 16.

Images