Mesh wireless local area network peering with multi-link operation

Abstract

A method of peering in a wireless mesh network, the method comprising: peering of a first mesh device with a second mesh device, wherein the first mesh device is either a first peer mesh multi-link device, MLD, and the second mesh device is a second peer mesh MLD wherein each of the first and the second peer mesh MLDs comprise one or more affiliated mesh stations, STAs; or a mesh STA affiliated with a mesh MLD, and the second mesh device is a mesh STA; wherein peering is initiated after a discovery procedure is completed between the first mesh device and the second mesh device.

Description

[0001] MESH WIRELESS LOCAL AREA NETWORK PEERING WITH MULTI-LINK OPERATION

[0002] TECHNICAL FIELD

[0003] The present disclosure generally relates to methods and systems in the field of WLAN Mesh operations.

[0004] BACKGROUND OF THE INVENTION

[0005] A Basic Service Set, BSS, is an IEEE 802.11 definition of a set of stations that can communicate with each other either directly, e.g. a mesh network, or through an Access Point, AP, i.e. an infrastructure BSS. It is the basic network building block of an IEEE 802.il WLAN.

[0006] When a mesh STA, which does not support the functionalities of an Infrastructure BSS, initiates connectivity for a mesh basic service set, MBSS, in other words a mesh network, it attempts to discover other mesh STAs and it begins transmitting beacon frames advertising the MBSS identified by mesh network identifiers, which include a mesh ID and other parameters for mesh operation. Other mesh STAs then use traditional discovery mechanisms in IEEE 802.11, such as:

[0007] Passive scan - receive Beacon or unsolicited Probe Response frames that includes mesh network identifiers;

[0008] Active scan - transmit Probe Request frames / receive Probe Response frames that includes mesh network identifiers.

[0009] IEEE 802.11 defines communications requirements for STAs that operate in a mesh network. Mesh STAs discover and peer with each other to form mesh links. Data frames can be routed between peer mesh STAs through a series of hops through other mesh STAs operating in a mesh network.

[0010] In a typical Mesh Architecture that may be implemented according to IEEE 802.11, information is exchanged between the mesh and external infrastructure, e.g. a BSS 1 at a STA 1, or a LAN at a STA 4. Mesh peering links are associated links, e.g. with established security between the Mesh STAs. These links are typically within the same WLAN frequency band, e.g. 2.4 GHz.

[0011] Given various STAs in a mesh network, e.g. STA 1 , STA 2, STA 3, STA 4, with STA 1 being the first STA and STA 4 being the last STA, these are peers in the mesh network. A frame originating at, e.g., STA 1 with a destination of STA 4, will be relayed through STA 2 and STA 3 to STA 4.

[0012] Mesh “peering “is a distributed, non-hierarchical, and non-exclusive unidirectional agreement to communicate between a pair of mesh STAs. Peering takes place after mesh discovery.

[0013] IEEE 802.1 Ibe has introduced a multi-link device, MLD. In infrastructure BSS WLAN, MLDs communicate over multiple WLAN links between an AP MLD and non-AP MLD. MLDs allow traffic exchange on multiple links providing a performance gain of using multiple channels.

[0014] In particular, each AP MLD may have one or more affiliated APs, where each affiliated AP is communicating with a different link connected to a STA affiliated with the non-AP MLD. Similarly, each non-AP MLD has one or more affiliated non-AP STAs, where each affiliated non-AP STA is operating on a different link. IEEE 802.11 be also introduces dynamic link transitions, where traffic can be moved from one link to another, as the non-AP STA affiliated with the non-AP MLD, operating on one of the links, can be in active mode or in power save mode.

[0015] An IEEE 802.11 a Reduced Neighbor Report, RNR, element is included in Beacon and Probe Response frames and it contains channel and other quintessence information about neighbor APs and APs affiliated with the same AP MLD, an affiliated AP, as the reporting AP Each affiliated AP transmits the Beacon and Probe Response frames with this information.

[0016] A Multi-Link Element, MLE, includes detailed information corresponding to other links of the same MLD. The affiliated AP or affiliated non-AP STA of that MLD, transmit the frame in which the MLE is included.

[0017] SUMMARY

[0018] Currently, very little work has been done in the standard amendments IEEE 802.1 Ibe and IEEE 802.1 Ibn to support multi-link operation, MLO, with mesh networking. There are multiple aspects of mesh features that need to be updated in order to take care of MLO.

[0019] The present disclosure attempts to mitigate this situation. The present disclosure relates to peering aspects for mesh MLO. MLO peering takes place after mesh multi-link operation, MLO, discovery procedure has completed.

[0020] The present disclosure is defined by the scope of the independent claims. The dependent claims provide advantageous embodiments of the present disclosure.

[0021] The following terminology is used throughout this document: “mesh STA” refers to a STA that follows requirements mesh networking as defined in the current IEEE 802.11-2020 standard; “mesh MLD” refers to an MLD that follows the requirements for mesh operation; a mesh MLD transmits traffic to a peer mesh MLD through one or more of its “affiliated STAs”; and an “affiliated mesh STA” is a STA that is affiliated with a mesh MLD that exchanges traffic with a peer mesh STA.

[0022] A first aspect of a method of peering in a wireless mesh network is, the method comprising: peering of a first mesh device with a second mesh device, wherein the first mesh device is either a first peer mesh multi-link device, MLD, and the second mesh device is a second peer mesh MLD wherein each of the first and the second peer mesh MLDs comprise one or more affiliated mesh stations, STAs; or a mesh STA affiliated with a mesh MLD, and the second mesh device is a mesh STA; wherein peering is initiated after a discovery procedure is completed between the first mesh device and the second mesh device.

[0023] According to an implementation of the method of the first aspect, in case the second mesh device is a mesh STA, mesh data may be exchanged between the mesh STA and an affiliated mesh STA of the first peer mesh MLD after the peering procedure between the mesh STA and the mesh STA affiliated with the mesh MLD is completed. According to an implementation of the method of the first aspect, the method may further include: the peering procedure is a unidirectional procedure; wherein in case peering takes place between the first peer mesh MLD and the second peer mesh MLD, the peering comprises: transmitting, by the first peer mesh MLD being an initiating peer mesh MLD, to the second peer mesh MLD being a solicited peer mesh MLD a frame for opening the mesh peering, Mesh Peering Open frame; receiving, by the initiating peer mesh MLD, after the transmission of the Mesh Peering Open frame, a frame for confirming the mesh peering, Mesh Peering Confirm frame, transmitted by the solicited peer mesh MLD to complete the peering.

[0024] According to an implementation of the method of the first aspect, the method may further include: the initiating peer mesh MLD transmits the Mesh Peering Open frame through one of its affiliated STAs, the solicited peer mesh MLD receives the Mesh Peering Open frame through one of its affiliated STAs, and the solicited peer mesh MLD transmits the Mesh Peering Confirm frame through the same affiliated STA.

[0025] According to an implementation of the method of the first aspect, the method may further include: the Mesh Peering Open frame includes a multi-link element, MLE, the multi-link element includes a set of links requested to be setup for use for mesh data communication between the initiating peer mesh MLD and the solicited peer mesh MLD.

[0026] According to an implementation of the method of the first aspect, the method may further include: the Mesh Peering Confirm frame includes a multi-link element, MLE, the multi-link element contains a subset of the links requested by the initiating peer mesh MLD and are accepted by the solicited peer mesh MLD for use for mesh data communication.

[0027] According to an implementation of the method of the first aspect, the method may further include: the set of links, requested by the initiating peer mesh MLD and accepted by the solicited peer mesh MLD, is unidirectional to be used by the peer mesh MLD that has initiated the peering, when it initiates the transmission of frames to the peer mesh MLD that have been solicited for a peering.

[0028] According to an implementation of the method of the first aspect, the method may further include: any of the peer mesh MLDs may transmit a frame for closing the mesh peering, Mesh Peering Close frame, on any of the setup links between transmitting mesh MLD and the peer mesh MLD, for terminating the data exchange between the initiating peer mesh MLD and the solicited peer mesh MLD.

[0029] According to an implementation of the method of the first aspect, the method may further include: a single set of primitives is used by the Station Management Entity, SME, of the MLD for all mesh peering related operations for the transmission of Mesh Peering Open, Mesh Peering Confirm, and Mesh Peering Close frames, wherein in order to support mesh multi-link operation, MLO: an additional parameter, is selected to distinguish peering between a mesh MLDs case and peering between an affiliated mesh STA and a mesh STA case, wherein in case the peering takes place between mesh MLDs, the additional parameter is included in the set of primitives, and in case the peering takes place between an affiliated mesh STA and a mesh STA, the additional parameter is not included in the set of primitives, wherein the additional parameter is a conditional parameter; or an additional parameter is selected, wherein the value of the additional parameter is used to distinguish peering between a mesh MLDs case and peering between an affiliated mesh STA and a mesh STA case, wherein if the value of the additional parameter is 1 the peering takes place between mesh MLDs, and if the value of the additional parameter is 0 the peering takes place peering between mesh MLDs and peering between an affiliated mesh STA and a mesh STA, wherein the additional parameter is a fixed parameter; or the presence of a multi-link element as a parameter in the set of primitives and in the corresponding peering frames is used to indicate peering between mesh MLDs.

[0030] According to an implementation of the method of the first aspect, the additional parameter may be referred to as MeshMACAddress parameter.

[0031] According to an implementation of the method of the first aspect, the method may further include: in case the additional parameter is selected to distinguish a case of peering between peer mesh MLDs, and a case of peering between an affiliated mesh STA and a mesh STA, discovering, by any peer mesh MLD, or a peer mesh STA, wherein: if a solicited peer mesh MLD is discovered, issuing, by the initiating peer mesh MLD, a request primitive with the additional parameter set to the initiating peer mesh MLD MAC Address and setting a parameter of the peer MAC address to the MAC Address of the solicited peer mesh MLD, wherein the frame body of the Mesh Peering Open frame includes the MLE; if a peer mesh STA is discovered, issuing, by the initiating STA affiliated with a peer mesh MLD a request primitive including no additional parameter and setting a parameter of the peer MAC address to the MAC Address of the solicited mesh STA, wherein the frame body of the Mesh Peering Open frame does not include the MLE.

[0032] According to an implementation of the method of the first aspect, the request primitive may be referred to as MESHPEERINGMANAGEMENT.request.

[0033] According to an implementation of the method of the first aspect, the method may further include: the process for the solicited peer mesh MLD responding to a mesh peering request comprises: receiving a Mesh Peering Open frame through a STA affiliated with the peer mesh MLD, the SME of the peer mesh MLD generates an indication primitive, wherein: if the MLE is included in the Mesh Peering Open frame, the additional parameter is set to the initiating mesh MLD MAC Address; if the additional parameter is present in the received indication primitive, issuing, by the SME of the solicited peer mesh MLD, a response primitive with the additional parameter set to the solicited peer mesh MLD MAC Address and the parameter of the peer MAC address set to the MAC Address of the initiating peer mesh MLD; wherein an MLE is included in a confirm primitive and is transmitted in the Mesh Peering Confirm frame; if the additional parameter is not present in the received indication primitive, issuing, by the SME of the second peer mesh MLD, a response primitive with no additional parameter and the parameter of the peer MAC address set to the MAC Address of the peer mesh STA, wherein an MLE is not included in the confirm primitive and is not transmitted in the Mesh Peering Confirm frame.

[0034] According to an implementation of the method of the first aspect, the indication primitive may be referred to as MESHPEERINGMANAGEMENT.indication primitive; and / or the response primitive may be referred to as MESHPEERINGMANAGEMENT.response primitive; and / or the confirm primitive may be referred to as MESHPEERINGMANAGEMENT.confirm primitive.

[0035] According to an implementation of the method of the first aspect, wherein in case peering is successfully performed between an affiliated mesh STA and a mesh STA, the method may further comprise establishing a security association by the peer mesh MLD with the mesh STA.

[0036] According to an implementation of the method of the first aspect, the method may further comprise, establishing the security association further comprises the affiliated mesh STA establishing a security association with the mesh STA including both a pairwise key and group key.

[0037] According to an implementation of the method of the first aspect, the method may further include: in case peering is successfully performed between the peer mesh MLDs, the connection is established between the peer mesh MLDs and data is transmitted across the links within the security association; wherein these links are referred to as setup links, wherein transmitting data across setup links comprises cryptographically encapsulating data frames at upper MAC layer.

[0038] According to an implementation of the method of the first aspect, the method may further include: cryptographically encapsulating data frames at the upper MAC comprises calculating Additional Authentication Data, AAD, using the peer mesh MLD MAC address of the respective peer mesh MLDs.

[0039] According to an implementation of the method of the first aspect, the method may further include: group key management and group addressed cryptographic encapsulation is performed at the respective peer mesh MLDs.

[0040] According to an implementation of the method of the first aspect, wherein the method may further comprise: in case peering is performed between the peer mesh MLDs, the respective peer mesh MLD MAC address is used to define a relay point for the next hop; in case peering is performed between an affiliated mesh STA and a mesh STA, with respect to the mesh STA, the MAC address of the mesh STA affiliated with the peer mesh MLD is used to define the relay point for the next hop, wherein the MAC address of the peer mesh MLD will be automatically defined as the next relay hop for each of the mesh STAs affiliated with that peer mesh MLD.

[0041] According to an implementation of the method of the first aspect, wherein if two or more setup links are negotiated during the peering procedure between mesh MLDs, the transmitting peer mesh MLD may select which setup link, is used to send traffic on a frame by frame basis.

[0042] The present disclosure further provides a second aspect of a mesh device in a wireless mesh network, wherein: the mesh device is configured to peer with a second mesh device, wherein the mesh device is either: a first peer mesh multi-link device, MLD, and the second mesh device is a second peer mesh MLD wherein each of the first and the second peer mesh MLDs comprise one or more affiliated mesh stations, STAs; or the mesh device is a mesh STA affiliated with a mesh MLD, and the second mesh device is a mesh STA; wherein the mesh device is configured to initiate peering after a discovery procedure is completed between the first mesh device and the second mesh device.

[0043] According to an implementation of the device of the second aspect, wherein in case the second mesh device is a mesh STA, mesh data may be exchanged between the mesh STA and an affiliated mesh STA of the first peer mesh MLD.

[0044] According to an implementation of the device of the second aspect, wherein the peering procedure may be unidirectional; wherein in case peering takes place between the first peer mesh MLD and the second peer mesh MLD, the peering may comprise: the first peer mesh MLD, being an initiating peer mesh MLD, is configured to transmit to the second peer mesh MLD, being a solicited peer mesh MLD, a frame for opening the mesh peering, Mesh Peering Open frame; the initiating peer mesh MLD, after the transmission of the Mesh Peering Open frame, is configured to receive a frame for confirming the mesh peering, Mesh Peering Confirm frame, transmitted by the solicited peer mesh MLD to complete the peering.

[0045] According to an implementation of the device of the second aspect, wherein the initiating peer mesh MLD may be configured to transmit the Mesh Peering Open frame through one of its affiliated STAs, the solicited peer mesh MLD may be configured to receive the Mesh Peering Open frame through one of its affiliated STAs, and the solicited peer mesh MLD may be configured to transmit the Mesh Peering Confirm frame through the same affiliated STA.

[0046] According to an implementation of the device of the second aspect, the Mesh Peering Open frame may include a multi-link element, MLE, the multi-link element that includes a set of links requested to be setup for use for mesh data communication between the initiating peer mesh MLD and the solicited peer mesh MLD. According to an implementation of the device of the second aspect, the Mesh Peering Confirm frame may include a multi-link element, MLE, the multi-link element includes a subset of the links requested by the initiating peer mesh MLD and are accepted by the solicited peer mesh MLD for use for mesh data communication.

[0047] According to an implementation of the device of the second aspect, the set of links, requested by the initiating peer mesh MLD and accepted by the solicited peer mesh MLD, may be unidirectional to be used by the peer mesh MLD that has initiated the peering, when it initiates the transmission of frames to the peer mesh MLD that have been solicited for a peering.

[0048] According to an implementation of the device of the second aspect, wherein any of the peer mesh MLDs may transmit a frame for closing the mesh peering, Mesh Peering Close frame, on any of the setup links between transmitting mesh MLD and the peer mesh MLD, for terminating the data exchange between the initiating peer mesh MLD and the solicited peer mesh MLD.

[0049] According to an implementation of the device of the second aspect, the device may be further configured to comprise: a single set of primitives is used by the Station Management Entity, SME, of the MLD for all mesh peering related operations for the transmission of Mesh Peering Open, Mesh Peering Confirm, and Mesh Peering Close frames, wherein in order to support mesh multi-link operation, MLO: an additional parameter is selected to distinguish peering between a mesh MLDs case and peering between an affiliated mesh STA and a mesh STA case, wherein in case the peering takes place between mesh MLDs, the additional parameter is included in the set of primitives, and in case the peering takes place between an affiliated mesh STA and a mesh STA, the additional parameter is not included in the set of primitives, wherein the additional parameter is a conditional parameter; or an additional parameter is selected, wherein the value of the additional parameter is used to distinguish peering between a mesh MLDs case and peering between an affiliated mesh STA and a mesh STA case, wherein if the value of the additional parameter is 1 the peering takes place between mesh MLDs, and if the value of the additional parameter is 0 the peering takes place peering between mesh MLDs and peering between an affiliated mesh STA and a mesh STA, wherein the additional parameter is a fixed parameter; or the presence of a multi-link element as a parameter in the set of primitives and in the corresponding peering frames is used to indicate peering between mesh MLDs.

[0050] According to an implementation of the device of the second aspect, the additional parameter may be referred to as MeshMACAddress parameter. According to an implementation of the device of the second aspect, the device may be further configured to: in case an additional parameter is selected to distinguish a case of peering between peer mesh MLDs, and a case of peering between an affiliated mesh STA and a mesh STA, the mesh device being any of peer mesh MLD, or peer mesh STA is configured to start discovering, wherein: if a solicited peer mesh MLD is discovered, the initiating peer mesh MLD is configured to issue a request primitive with the additional parameter set to the initiating peer mesh MLD MAC Address and to set a parameter of a peer MAC address to the MAC Address of the solicited peer mesh MLD, wherein the frame body of the Mesh Peering Open frame includes the MLE; if a peer mesh STA is discovered, issuing, the initiating STA affiliated with a peer mesh MLD is configured to issue a request primitive including no additional parameter and to set the parameter of the peer MAC address parameter to the MAC Address of the solicited mesh STA, wherein the frame body of the Mesh Peering Open frame does not include the MLE.

[0051] According to an implementation of the device, the request primitive may be referred to as MESHPEERINGMANAGEMENT.request.

[0052] According to an implementation of the device of the second aspect, the device may be configured to: the process for the solicited peer mesh MLD responding to a mesh peering request comprises: receiving a Mesh Peering Open frame through a STA affiliated with the peer mesh MLD, the SME of the peer mesh MLD generates an indication primitive, wherein: if the MLE is included in the Mesh Peering Open frame, the additional parameter is set to the initiating mesh MLD MAC Address; if the additional parameter is present in the received indication primitive, issuing, by the SME of the solicited peer mesh MLD, a response primitive with the additional parameter set to the solicited peer mesh MLD MAC Address and the parameter of the peer MAC address set to the MAC Address of the initiating peer mesh MLD; wherein an MLE is included in a confirm primitive and is transmitted in the Mesh Peering Confirm frame; if the additional parameter is not present in the received indication primitive, issuing, by the SME of the second peer mesh MLD a response primitive with no additional parameter and the parameter of the peer MAC address set to the MAC Address of the peer mesh STA, wherein an MLE is not included in a confirm primitive and is not transmitted in the Mesh Peering Confirm frame.

[0053] According to an implementation of the device of the second aspect, the indication primitive may be referred to as MESHPEERINGMANAGEMENT.indication primitive; and / or the response primitive may be referred to as MESHPEERINGMANAGEMENT.response primitive; and / or the confirm primitive may be referred to as MESHPEERINGMANAGEMENT.confirm primitive. According to an implementation of the device of the second aspect, the device may be further configured to: in case peering is successfully performed between an affiliated mesh STA and a mesh STA, the mesh device is further configured to establish a security association by the peer mesh MLD with the mesh STA.

[0054] According to an implementation of the device of the second aspect, the device may be further configured to: establishing the security association further comprises the affiliated mesh STA establishing a security association with the mesh STA including both a pairwise key and group key.

[0055] According to an implementation of the device of the second aspect, wherein the device may be further configured to: in case peering is successfully performed between the peer mesh MLDs, the connection may be established between the peer mesh MLDs and data is transmitted across the links within the security association, wherein these links are referred to as setup links, wherein transmitting data across setup links comprises cryptographically encapsulating data frames at upper MAC layer.

[0056] According to an implementation of the device of the second aspect, wherein cryptographically encapsulating data frames at the upper MAC may comprise calculating Additional Authentication Data, AAD, using the peer mesh MLD MAC address of the respective peer mesh MLDs.

[0057] According to an implementation of the device of the second aspect, wherein group key management and group addressed cryptographic encapsulation may be performed at the respective peer mesh MLDs.

[0058] According to an implementation of the device of the second aspect, the device may further be configured to: in case peering is performed between the peer mesh MLDs, the respective peer mesh MLD MAC address is used to define a relay point for the next hop; in case peering is performed between an affiliated mesh STA and a mesh STA, with respect to the mesh STA, the MAC address of the mesh STA affiliated with the peer mesh MLD is used to define the relay point for the next hop, wherein the MAC address of the peer mesh MLD will be automatically defined as the next relay hop for each of the mesh STAs affiliated with that peer mesh MLD.

[0059] According to an implementation of the device of the second aspect, the device may be further configured to: if two or more setup links are negotiated during the peering procedure between mesh MLDs, the transmitting peer mesh MLD may select which setup link, is used to send traffic on a frame by frame basis.

[0060] The present disclosure further provides a fourth aspect of a computer program product comprising program code for performing the method according to the first aspect when executed on a computer or a processor.

[0061] The present disclosure further provides a fifth aspect of a non-transitory computer-readable medium carrying a program code which, when executed by a computer device, causes the computer device to perform the method according to the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In the following, embodiments of the invention are described in more detail with reference to the attached figures and drawings, in which:

[0063] FIG. 1 illustrates schematically an example of MBSS Operation.

[0064] FIG. 2 illustrates a principle of MBSS Peering.

[0065] FIG. 3 illustrates a known Mesh Architecture.

[0066] FIG. 4 illustrates an example of Multi-Link Operation.

[0067] FIG. 5 illustrates an example of an MLO Mesh Topology.

[0068] FIG. 6 illustrates a Multi-Link Element format.

[0069] FIG. 7 illustrates a Multi-Link Control field format of the MLE of FIG. 6.

[0070] FIG. 8 illustrates a Per-STA Profile subelement format of the Basic MLE format of FIG. 6.

[0071] FIG. 9 shows a table indicating Mesh Peering Management Response primitive parameters.

[0072] FIG. 10 illustrates Mesh peering between a mesh MLD and a mesh STA.

[0073] FIG. 11 illustrates Routing of traffic in a mesh network with mesh MLDs.

[0074] DESCRIPTION

[0075] FIG. 1 illustrates several mesh STAs scanning and discovering peers. In this example, when a mesh STA (i.e. a non-AP STA not supporting the functionalities of an Infrastructure BSS), initiates connectivity for a mesh basic service set, MBSS, in other words a mesh network, it attempts to discover other mesh STAs in its proximity and it begins transmitting beacon frames advertising the MBSS. Other mesh STAs then use traditional discovery mechanisms in IEEE 802.11, such as: i) a passive scan, i.e. listening for Beacon or unsolicited Probe Response frames; ii) an active scan, i.e. transmitting a Probe Request and / or receiving a Probe Response.

[0076] In FIG. 1, a “mesh profile” identifies the MBSS and is included in Beacon and Probe Response frames. The mesh profile includes a “Mesh ID”, e.g. an Information Element in management frames, which identifies an instance of an MBSS.

[0077] IEEE 802.11 defines communications requirements for STAs that operate in a mesh network. Mesh STAs discover and peer with each other to form mesh links. Data can be routed between peer mesh STAs through a series of hops through other STAs operating in a mesh network. For example, as illustrated for explanatory purposes in FIG. 1, STA O, STA A, STA B, and STA D are peers in a mesh network. These STAs may also be designated as Mesh STAs. FIG. 2 illustrates MBSS Peering initiation and termination procedure. Mesh “peering “is a distributed, non-hierarchical, and non-exclusive unidirectional agreement to communicate between a pair of mesh STAs. Mesh MLO Peering takes place after mesh MLO discovery procedure is completed.

[0078] Each mesh STA manages its own peering with other mesh STAs. The Peering Establishing Protocol is a true peer-to-peer protocol. Each side offers and agrees to parameters that define the terms of the peering and govern communication. Two modes are supported:

[0079] • secured peering (AMPE).

[0080] • unsecured peering (MPM).

[0081] The peering process is as follows:

[0082] • Each side must make an offer of attributes to use for a potential peering between itself and the other peer mesh STA.

[0083] • Each side must confirm the agreed-upon attributes that define the peering between the other peer mesh STA and itself.

[0084] • After each side has either been confirmed for its offer or has confirmed agreement, i.e. that is initiated by peer mesh STA, the peering is established.

[0085] • Each peer mesh STA needs to initiate a peering independently and both sides can initiate the peering simultaneously.

[0086] • A peer mesh STA initiates peering by sending a Mesh Peering Open frame to a peer mesh STA.

[0087] • The receiving mesh STA evaluates the contents of the Mesh Peering Open frame and sends a Mesh Peering Confirm frame to establish a link with the initiating peer mesh STA.

[0088] • Either one of the peer mesh STAs can terminate the peering by sending a Mesh Peering Close frame to its peer mesh STA.

[0089] This process is summarized in FIG. 2. FIG. 2 illustrates an initiator, e.g. a smartphone and another initiator, e.g. a notebook computer. In this example, these two devices are the mesh peers. Both the smartphone as well as the notebook computer may transmit a Mesh Peering Open frame. The respective other of the two may send a Mesh Peering Confirm. Afterwards, bidirectional communication, i.e. bi-directional mesh data communication, may be performed between these two peers. Either peer may terminate the respective link.

[0090] A mesh profile identifies the MBSS and is included in Beacon and Probe Response frames. The mesh profile includes a “Mesh ID”, e.g. an Information Element in management frames, which identifies an instance of an MBSS.

[0091] For explanatory purposes, FIG. 3 illustrates a typical Mesh Architecture that may be implemented by IEEE 802.11-2020 standard. Mesh Gates shown in FIG. 3 allow for exchanging of information between the mesh STA and external infrastructure, e.g. a BSS 1 at mesh STA 1, or a LAN at mesh STA 4. Here, in FIG. 3, mesh peering links are associated links, e.g. with established security between the Mesh STAs. Mesh peering links, e.g. with established security, allow traffic to be transmitted between the Mesh STAs. These links are typically within the same WLAN frequency band, e.g. 2.4 GHz.

[0092] IEEE 802.1 Ibe has introduced a multi-link operation, MLO. An MLO is shown for explanatory purposes in FIG. 4. The MLO includes at least two or more multi-link devices, MLDs which can communicate over multiple WLAN links between an AP MLD, item 201 , and non-AP MLD, item 203. This communication allows for traffic exchange on multiple links and it provides a performance gain of using multiple channels.

[0093] In explanatory FIG. 4, the AP MLD 201 has one or more affiliated APs. For explanatory purposes three affiliated APs, items 201.1, 201.2 and 201.3 are shown in FIG. 4, however the number of affiliated APs may be different. In this example, item 201.1 denotes a 2.4 GHz AP, item 201.2 denotes a 5 GHz AP, and item 201.3 denotes a 5 GHz AP Each affiliated AP; in particular each of APs 201.1, 201.2, and 201.3 is operating on a different link. Similarly, the non-AP MLD 203 has one or more affiliated non-AP STAs. For explanatory purposes, two affiliated STAs, items 203.1 and 203.2 are shown in FIG. 4, however the number of affiliated STAs of item 203 may be different. In this example, item 203.1 denotes a 2.4 GHz STA, here also indicated as STA1, and item 203.2 denotes a 5 GHz STA, here also indicated as STA2. Each affiliated non-AP STA, in particular item 203.1, i.e. STA1, and item 203.2, i.e. STA2, is operating on a different link. In the example shown in FIG. 4, the AP MLD has three different links. The non-AP MLD has been associated with the AP MLD by setting up two links with the AP MLD, on which the frames exchanged between the AP MLD and the specific non-AP MLD can be transmitted.

[0094] IEEE 802.1 Ibe also introduces dynamic link transitions, where traffic can be moved from one link to another, as the affiliated non-AP STA, operating on one of the links, can be in active mode or in power save mode.

[0095] FIG. 5 illustrates the mesh MLO network architecture, according to the present disclosure. The primary difference between the architecture show in FIG. 5 and the mesh architecture shown in FIG. 3 is that the Mesh MLDs in FIG. 5 are able to exchange frames using multiple links in multiple WLAN bands simultaneously. FIG. 5 illustrates three Mesh MLDs, 10, 20, and 30. The number of Mesh MLDs being (only) three is just selected for explanatory purposes. FIG. 5 illustrates Mesh peering between Mesh MLDs of the Mesh MLO architecture, e.g. Mesh MLDs 10 and 20, using two links: Link 1: 2.4 GHz Ch(annel) 1, Link 2: 5 GHz Ch 165. FIG. 5 further illustrates Mesh peering with three links between Mesh MLDs 10 and 30: Link 1 : 2.4 GHz Ch 1, Link 2: 5 GHz Ch 165, and Link 3: 6 GHz Ch 73. FIG. 5 further illustrates Mesh peering with three links between Mesh MLDs 20 and 30: Link 1 : 2.4 GHz Ch 1 Link 2: 5 GHz Ch 165.

[0096] In addition, FIG. 5 shows an additional mode of operation in mesh MLO network, where one of the mesh STAs affiliated with mesh MLD2 (20), has 2 peer mesh STAs (also referred to as “legacy mesh STA” in FIG. 5). This is done within the mesh BSS1 that is established by one of the mesh STAs affiliated with the Mesh MLD 2 (20). This mode will be further detailed in the following sections (as well as supported by several claims hereinafter).

[0097] With regard to FIG. 6, a Multi-Link Element is introduced. The Multi-Link Element, MLE, 100 includes parameters and capabilities information corresponding to the other links of the same MLD, cf. FIG. 5, that the AP or non-AP STA, transmitting the frame in which the MLE is included, are affiliated with. The format of the MLE 100 is shown in FIG. 6 for explanatory purposes. Thus, FIG. 6 illustrates the format of an MLE. The MLE 100, e.g. as illustrated in FIG. 6, is carried mainly in Beacon, Probe Response, Authentication, Association Request and Association Response frames when exchanged between MLDs using one of the affiliated APs / non-AP STAs.

[0098] The MLE of FIG. 6 includes an Element ID field 100-1, a Length field 100-2, an Element ID Extension field 100-3, a MultiLink Control field 100-4, a Common Info field 100-5 and a Link-Info field 100-6. The length / width of these respective fields, measured in octets, is indicated in FIG. 6. Specifically, as shown in FIG. 6, the MLE 100 comprises the Multi-Link Control field 100-4. In FIG. 7, the Multi-Link Control field format 100-4 of FIG. 6 is further illustrated. The Multi-Link Control field 100-4 differentiates the types of MLE, as shown in FIG. 7. FIG. 7 indicates that the Multi-Link Control field 100-4 comprises a Type subfield 100-4.1, a reserved subfield 100-4.2 and a Present Bitmap subfield 100-4.3. The number of bits included in each of these subfields is indicated in FIG. 7.

[0099] The MLE 100 of FIG. 6 further includes a field carrying parameters and capabilities that are applicable to all links, i.e. common information. This field is called a Common Info field 100-5. The Common Info field 100-5, cf. FIG. 6, carries information that is common to all the links, cf. FIG. 5.

[0100] The MLE 100 of FIG. 6 further includes a field carrying specific information for each link. This field is called a Link Info field 100-6, cf. FIG. 6. The Link Info field 100-6 of the MLE 100 carries specific parameters and capabilities that are applicable to each link, cf. affiliated STAs of FIG. 4. Each of these information elements is called a Per-STA Profile subelement. Thus, the Link Info field 100-6 of FIG. 6, comprises subelements, each specific per affiliated STA, i.e. Per-STA Profile subelement. The Link Info field 100-6 carries one Per-STA Profile subelement corresponding to each STA affiliated with the MLD, e.g. the MLDs of FIG. 5. The format of a Per-STA Profile subelement 100-6.5 of the basic MLE 100 is shown in FIG. 8. FIG. 8 thus illustrates the details of the Link-Info field 100-6. The Per-STA Profile subelement 100-6 of FIG. 8 includes a Subelement ID subfield 100-6.1, a Length subfield 100-6.2, a STA Control subfield 100-6.3, a STA Info subfield 100-6.4 and the aforementioned STA Profile subfield 100-6.5. The length / width of the subfields of the Link-Info subfield 100-6, measured in octets, is given in FIG. 8.

[0101] It should be noted that during the process of MLD discovery, the Link Info field 100-6 is not included within the basic MLE 100 carried in the Beacon and Probe Response frames, as described in the IEEE 802.1 Ibe amendment.

[0102] Furthermore, an access point, AP, may transmit a multi-link Probe Response, wherein the AP is affiliated with an AP multi-link device, MLD. The Probe Response frame is transmitted in response to a multi-link probe request and carries an MLE to provide a complete or partial profile of one or more APs affiliated with a specific AP MLD as defined in the IEEE 802.11 be amendment.

[0103] According to the present disclosure, there are two operating modes for mesh MLO:

[0104] • Mode 1 : Peering between mesh MLDs, where each mesh MLD negotiates a set of links for mesh operation.

[0105] • Mode 2: Peering between a STA affiliated with a mesh MLD (referred to as an affiliated mesh STA) and a mesh STA.

[0106] In the first mode, Mode 1 , Mesh MLDs can peer and exchange frames through negotiated setup links:

[0107] • The peering procedure between the mesh MLDs includes the same frame exchange that is described in FIG. 2, where: 1.The frames are exchanged through one of the mesh STA affiliated with the mesh MLD.

[0108] 2. The frames include the MLE which carry the parameters and information related to all the links that should be setup between the mesh MLDs.

[0109] • When peering is completed between MLDs, communications can be established on multiple negotiated setup links and frame exchanges take place between peer MLDs via affiliated STAs.

[0110] • The set of links negotiated between an initiator mesh MLD and a responder mesh MLD upon successful peering, is not required to be the same set of links negotiated when the responder mesh MLD completes peering with the initiator mesh MLD. In other words, the set of negotiated links can be different in each direction.

[0111] • When MLD mesh peers negotiate two or more sets of links, data frames may be exchanged on one or more different links.

[0112] In the second mode, Mode 2, an affiliated mesh STA can peer with a mesh STA and exchange frames on the link it is operating:

[0113] • The peering procedure between the mesh STA and the mesh STA affiliated with mesh MLD includes the same frame exchange that is described in FIG. 2,

[0114] • Mesh data is exchanged between the mesh STA and the affiliated mesh STA.

[0115] • The affiliated mesh STA relays the traffic through the mesh MLD.

[0116] Within this context, this may also be viewed as peering between mesh devices. Thus, a first mesh device may either be a first peer mesh MLD and the second mesh device may be a second peer mesh MLD, wherein each of the first and the second peer mesh MLDs comprise one or more affiliated mesh stations, STAs. On the other hand, the first mesh device may be a mesh STA affiliated with a mesh MLD, and the second mesh device is a mesh STA.

[0117] A method of the present disclosure then relates to peering of the first mesh device with the second mesh device, wherein peering is initiated after a discovery procedure is completed between the first mesh device and the second mesh device.

[0118] Relaying of mesh traffic is updated to accommodate mesh links between two mesh MLDs, or an affiliated mesh STA and a mesh STA.

[0119] Building upon the method as indicated above, a first embodiment of the present disclosure relates to Mesh Peering between mesh MLDs using MLE that will be carried in the existing mesh peering related frames, such as: Mesh Peering Open frame, etc. Here, the peering procedure is unidirectional. According to the first embodiment of the present disclosure, wherein in case peering takes place between the first peer mesh MLD and the second peer mesh MLD, the peering comprises: transmitting, by one of the mesh STA affiliated with the first peer mesh MLD being an initiating peer mesh MLD, to the one of the mesh STA affiliated with the second peer mesh MLD being a solicited peer mesh MLD and is operating on the same link, a frame for opening the mesh peering, Mesh Peering Open frame; and receiving, by the same mesh STA affiliated with the initiating peer mesh MLD, in response to the Mesh Peering Open frame, a frame for confirming the mesh peering, Mesh Peering Confirm frame, transmitted by the same mesh STA affiliated with the solicited peer mesh MLD to complete the peering.

[0120] After a mesh MLD discovers a peer mesh MLD and elects to perform mesh peering, the initiating mesh MLD transmits a Mesh Peering Open frame through an affiliated mesh SPA to the peer Mesh MLD (on a common link that each of the MLDs have and is operating on the same channel). When peering takes place between mesh MLDs, the Mesh Peering Open frame includes an MLE with a set of the requested links to be used for mesh data communication between these MLDs.

[0121] The peer mesh MLD receives the Mesh Peering Open frame through an affiliated mesh STA and transmits a Mesh Peering Confirm frame through the same affiliated mesh STA to the corresponding mesh STA affiliated with the initiating mesh MLD to successfully complete the peering process. When peering takes place between the mesh MLD and the peer mesh MLD, the Mesh Peering Confirm frame includes an MLE with a set or subset of the accepted links by the peer MLD to be used for mesh data communication.

[0122] The set of negotiated links between peer mesh MLDs is unidirectional so that the negotiated links can be different in different direction. The mesh MLD will initiate peering with the peer mesh MLD and negotiate one set of links. The peer mesh MLD will initiate peering with the mesh MLD and negotiate another set of links.

[0123] After successful peering, either peer mesh MLD can transmit a Mesh Peering Close frame on any of the setup links between the mesh MLDs, using one of the mesh STA affiliated with the mesh MLD, to terminate the data exchange between the two MLDs.

[0124] After successful peering, Link Reconfiguration Notify / Request / Response frames can be used to modify the negotiated links (i.e. add or remove).

[0125] The current Mesh Peering Open / Confirm / Close frames are extended to manage mesh MLD peering, using the MLE, as described above.

[0126] The MLE used in Mesh Peering Open / Confirm / Close messages can be either the Basic MLE with Link Info, i.e. defined in 802.1 Ibe, as shown in FIG. 6, or a Mesh MLE.

[0127] Thus, the first embodiment establishes mesh peering between MLDs using a multi-link element.

[0128] The present disclosure further discloses a second embodiment of the present disclosure.

[0129] As mentioned above there are two mesh peering modes:

[0130] • between mesh MLDs, and

[0131] • between an affiliated mesh STA and a mesh STA.

[0132] In IEEE 802.11, the Station Management Entity, SME, uses a single set of primitives for all mesh peering related operations for initiating the transmission of Mesh Peering Open, Mesh Peering Confirm, and Mesh Peering Close frames.

[0133] • MESEIPEERINGMANAGEMENT (.request, .indication, .response and .confirm). For example, in IEEE 802.11-2020, the parameters for MESHPEERINGMANAGEMENT.response are given in the table as shown in FIG. 9.

[0134] It should be understood that the names for the respective frames might be subject to change and that e.g. MESI IPFF RINGMANAGF MENT.response is just one example for a name of a response frame.

[0135] Within this context, there are three options:

[0136] Option 1 : According to this option, to support mesh MLO, it is required to include a conditional MeshMACAddress parameter to distinguish between the mesh MLD and affiliated mesh STA peering modes. When the peering takes place between mesh MLDs, the conditional MeshMACAddress parameter is included. When the peering takes place between an affiliated mesh STA and a mesh STA, the conditional MeshMACAddress parameter is not included.

[0137] Option 2: According to this option, to support mesh MLO, it is required to include a fixed, i.e. non-conditional MeshMACAddress parameter, where its value is used to distinguish between the mesh MLD and affiliated mesh STA peering modes.

[0138] Here, again it should be understood that the additional conditional parameter may be referred to as MeshMACAddress parameter. However, this name is merely an example for this parameter and different names may be possible.

[0139] For example: If it set to 1, the peering takes place between mesh MLDs; if it is set to 0, the peering takes place between an affiliated mesh STA and a mesh STA.

[0140] Option 3: According to this option, an alternative to adding an additional parameter to the primitives would be to treat the presence of the MLE in the peering frames to indicate peering between mesh MLD peers.

[0141] The following description assumes that a parameter is added to the primitives.

[0142] When option 1 is applied, the process for MLD initiating the mesh peering may be defined as follows:

[0143] A mesh MLD performs mesh discovery procedures and discovers either a peer mesh MLD or peer mesh STA, according to the two modes mentioned already above, viz:

[0144] 1 ) Mode 1 - If a peer mesh MLD is discovered, the mesh MLD issues an MESHPEERINGMANAGEMENT.request with the MeshMACAddress parameter set to the mesh MLD MAC Address and the peerMACAddress parameter set to the MAC Address of the peer mesh MLD. The frame body of the Mesh Peering Open frame includes an MLE, e.g. either a Basic or Mesh variant.

[0145] 2) Mode 2 - If a peer mesh STA is discovered, the mesh MLD issues an MESHPEERINGMANAGEMENT.request with no MeshMACAddress parameter and the peerMACAddress parameter set to the MAC Address of the peer mesh STA. The frame body of the Mesh Peering Open frame does not include an MLE. The process for an MLD responding to a mesh peering request may be defined as follows:

[0146] A mesh MLD receives a Mesh Peering Open frame through an affiliated STA, which generates a MESHPEERINGMANAGEMENT indication primitive.

[0147] If the MLE, e.g. either a Basic or Mesh variant, is included in the Mesh Peering Open frame, the MeshMACAddress parameter is set to the mesh MLD MAC Address.

[0148] Here, MESHPEERINGMANAGEMENT.request is just an example for a name of the request primitive, MESHPEERINGMANAGEMENT.indication primitive is an example for a name of the indication primitive; MESHPEERINGMANAGEMENTconfirm primitive is an example of a name of the confirm primitive.

[0149] 1) Mode 1 - If the MeshMACAddress parameter is present in the .indication primitive, the mesh MLD issues an MESHPEERINGMANAGEMENT.response primitive with the MeshMACAddress parameter set to the mesh MLD MAC Address and the peerMACAddress parameter set to the MAC Address of the peer mesh MLD. An MLE is included in the MESETEERINGMANAGEMENTconfirm primitive and transmitted in the Mesh Peering Confirm frame, e.g. Basic or Mesh variant.

[0150] 2) Mode 2 - If the MeshMACAddress parameter is not present in the .indication primitive, the mesh MLD issues an MESHPEERINGMANAGEMENT.response with no MeshMACAddress parameter and the peerMACAddress parameter set to the MAC Address of the peer, i.e. legacy, mesh STA. An MLE is not included in the MESEIPEERINGMANAGEMENT. confirm primitive and transmitted in the Mesh Peering Confirm frame, e.g. Basic or Mesh variant.

[0151] An example of the mesh peering messages between a mesh MLD and a mesh STA is shown in FIG. 10. In FIG. 10, reference sign 11 denotes a Mesh MLD 1. This Mesh MLD 1 , item 11 , may be similar to item 10 in FIG. 5. The Mesh MLD 1 , item 11 in FIG. 10 includes an affiliated Mesh STA 2, denoted by reference sign 11.2. FIG. 10 further illustrates a Mesh MLD 4, which may be a Gate, denoted by reference sign 31. Item 31 may be similar to item 30 of FIG. 5. Mesh MLD 4, item 31 , includes an affiliated Mesh STA 1, denoted by reference sign 31.1. FIG. 10 further shows a Mesh STA 2 denoted by reference sign 21. Arrows indicate communication between the various items of FIG. 10. In particular, in Mode 1 peering is used to establish a connection between Mesh MLD 1 and Mesh MLD 4, i.e. items 11 and 31. In Mode 2, peering is used to establish a connection between Mesh STA 2, i.e. item 21 , and affiliated Mesh STA 2, i.e. item 11.2, of Mesh MLD 1 ; as well as a connection between Mesh STA 2, i.e. item 21, and affiliated Mesh STA 1, i.e. item 31.1 of Mesh MLD 4.

[0152] In other words, the second embodiment describes two modes of mesh MLD peering from the SME perspective.

[0153] According to a further, i.e. third, embodiment, the present disclosure discloses the possibility of secured peering transmissions. The third embodiment allows the mesh MLO peering messages to be secure. Again, this will be discussed for the two modes, as defined above. For Mode 1 operation between two mesh MLDs:

[0154] When peer Mesh MLDs perform successful peering, the connection is established between MLDs and data is transmitted across the setup links.

[0155] • Frames are cryptographically encapsulated at the upper MAC layer, which means the Additional Authentication Data, AAD, is calculated using the MLD MAC address of the mesh MLD peers.

[0156] • When the frames are transmitted between peer affiliated mesh STAs, the RA and TA in the MPDU, A-MPDU, or MMPDU frame header are set to the affiliated mesh STA MAC address respectively.

[0157] • The SA and DA are set to the MAC address of the respective source and destination entities.

[0158] • Group key management and group addressed cryptographic encapsulation is performed at the mesh MLD.

[0159] For Mode 2 operation between a mesh MLD and a mesh STA:

[0160] • When a mesh MLD successfully peers with a mesh STA, a mesh STA affiliated with the mesh MLD establishes a security association with a mesh STA.

[0161] • The affiliated mesh STA establishes a security association with the mesh STA that includes both a pairwise key and group key.

[0162] According to a further, i.e. fourth, embodiment, the present disclosure discloses routing of traffic in a mesh with mesh MLDs. Thus, the fourth embodiment describes the addresses that are used for MLO peering:

[0163] For mode 1 , when the peering is between mesh MLDs, the MLD MAC address is used to define the relay point for the next hop.

[0164] For mode 2, when the peering is between an affiliated mesh STA and a mesh STA, the affiliated mesh STA of the mesh MLD is used to define the relay point for the next hop. The mesh MLD will be automatically defined as the next relay hop for each of its affiliated mesh STAs.

[0165] If two or more (setup) links are negotiated, the transmitting Mesh MLD peer can select which link, of the setup links it negotiated during the peering process, is used to send traffic on a frame-by-frame basis. Here, traffic identifier, HD, -to-link mapping could be applied to mesh data communications.

[0166] An example of routing is shown in FIG. 11.

[0167] FIG. 11 illustrates a Source STA 40, sending a frame to a Destination STA 48. En route to Destination STA 48, various Mesh MLDs and their respective affiliated mesh STAs participate. In Step 1 , the Source STA 40 sends the frame through the Mesh STA Al, item 42. As indicated by Step 2, the next hop for Mesh STA Al is item 44.2, i.e. affiliated mesh STA A2. Item 44.2 is a mesh STA affiliated with Mesh MLD Bl, item 44. Thus, Mesh MLD Bl acts as the next hop for mesh STA A2. In other words, mesh STA A2 relays the frame to Mesh MLD Bl . As indicated in FIG. 11 , mesh MLD Bl receives the frame from mesh STA A2, and then relays the received frame to the next hop, the next hop being a further mesh MLD, here Mesh MLD B2, item 46. However, relaying the frame from mesh MLD Bl to Mesh MLD B2 is achieved by step 3, i.e. transmitting the frame through a further affiliated mesh STA A3. Thus, the frame is transmitted through affiliated mesh STA A3, item 44.3, which is a mesh STA affiliated with Mesh MLD Bl . Affiliated mesh STA A3, i.e. item 44.3 transmits the frame to affiliated mesh STA A4, item 46.4 that is a mesh STA affiliated with Mesh MLD B2, item 46. Thus, in step 4, Mesh MLD B2, item 46, receives the frame through its / from its affiliated mesh STA A4, item 46.4. Finally, in step 5, Mesh MLD B2, item 46, transmits the frame to the Destination STA 48 through affiliated mesh STA A5, item 46.5. Affiliated mesh STA A5 is a mesh STA affiliated with Mesh MLD B2, item 46.

[0168] SUMMARY

[0169] Summarizing, the key points of the present disclosure are as follows:

[0170] 1 ) Mesh links can be established between

[0171] • mesh MLD peers;

[0172] • an affiliated mesh STA and a mesh STA.

[0173] 2) To enable peering between mesh MLDs, a mesh MLD adds an MLE within the peer open message. The MLE is either:

[0174] • a Basic Multi-Link Element, with Link Info, or

[0175] • a Mesh Multi-Link Element.

[0176] 3) Data can be exchanged between peer mesh MLDs over a negotiated link, in particular a negotiated setup link.

[0177] 4) When an affiliated mesh STA peers with a mesh STA:

[0178] • Existing mesh peering procedures are used to establish the mesh link.

[0179] • The affiliated mesh STA address is used as the next hop and relays traffic to the MLD and the mesh MLD is automatically defined as the next relay hop for each of its affiliated mesh STAs.

[0180] ABBREVIATIONS

[0181] AP Access Point

[0182] BSS Basic Service Set

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

[0184] DEM Delivery Traffic Indication Map

[0185] LAN Local Area Network

[0186] MAC Media Access Control

[0187] MBSS Mesh Basic Service Set MBCA Mesh Beacon Collision Avoidance

[0188] MCF Mesh Coordination Function

[0189] MCCA MCF Controlled Channel Access

[0190] ML Multi-Link MLD Multi-Link Device

[0191] MLE Multi-Link Element

[0192] MLO Multi-Link Operation

[0193] MLO MBSS Multi-Link Operation Mesh Basic Service Set

[0194] NSTR Number of Streams RNR Reduced Neighbor Report

[0195] STA Station

[0196] TBTT Target Beacon Transmission Time

[0197] TTD Traffic Identifier

[0198] TSF Timing Synchronization Function WLAN Wireless Local Area Network

Claims

CLAIMS1. A method of peering in a wireless mesh network, the method comprising: peering of a first mesh device with a second mesh device, wherein the first mesh device is either a first peer mesh multi-link device, MLD, and the second mesh device is a second peer mesh MLD wherein each of the first and the second peer mesh MLDs comprise one or more affiliated mesh stations, ST As: or a mesh STA affiliated with a mesh MLD, and the second mesh device is a mesh ST A: wherein peering is initiated after a discovery procedure is completed between the first mesh device and the second mesh device.

2. The method according to claim 1, wherein in case the second mesh device is a mesh STA, mesh data is exchanged between the mesh STA and an affiliated mesh STA of the first peer mesh MLD after the peering procedure between the mesh STA and the mesh STA affiliated with the mesh MLD is completed.

3. The method according to claim 1, wherein the peering procedure is a unidirectional procedure; wherein in case peering takes place between the first peer mesh MLD and the second peer mesh MLD, the peering comprises: transmitting, by the first peer mesh MLD being an initiating peer mesh MLD, to the second peer mesh MLD being a solicited peer mesh MLD a frame for opening the mesh peering, Mesh Peering Open frame; receiving, by the initiating peer mesh MLD, after the transmission of the Mesh Peering Open frame, a frame for confirming the mesh peering, a Mesh Peering Confirm frame, transmitted by the solicited peer mesh MLD to complete the peering.

4. The method according to claim 3, wherein the initiating peer mesh MLD transmits the Mesh Peering Open frame through one of its affiliated STAs, the solicited peer mesh MLD receives the Mesh Peering Open frame through one of its affiliated STAs, and wherein the solicited peer mesh MLD transmits the Mesh Peering Confirm frame through the same affiliated STA.

5. The method according to claim 3 or 4, wherein the Mesh Peering Open frame includes a multi-link element, MLE, wherein the multi-link element includes a set of links requested to be setup for use for mesh data communication between the initiating peer mesh MLD and the solicited peer mesh MLD.

6. The method according to claim 5, wherein the Mesh Peering Confirm frame includes a multi-link element, MLE, wherein the multi-link element includes a subset of the links requested by the initiating peer mesh MLD and are accepted by the solicited peer mesh MLD for use for mesh data communication.

7. The method according to claim 5 or 6, wherein the set of links, requested by the initiating peer mesh MLD and accepted by the solicited peer mesh MLD, is unidirectional to be used by the peer mesh MLD that has initiated the peering, when it initiates the transmission of frames to the peer mesh MLD that have been solicited for a peering.

8. The method according to any one of claims 3 to 7, wherein any of the peer mesh MLDs transmit a frame for closing the mesh peering, Mesh Peering Close frame, on any of the setup links between transmitting mesh MLD and the peer mesh MLD, for terminating the data exchange between the initiating peer mesh MLD and the solicited peer mesh MLD.

9. The method according to any one of claims 2 to 8, wherein a single set of primitives is used by the Station Management Entity, SME, of the MLD for all mesh peering related operations for the transmission of Mesh Peering Open, Mesh Peering Confirm, and Mesh Peering Close frames, wherein in order to support mesh multi-link operation, MLO: an additional parameter is selected to distinguish peering between a mesh MLDs case and peering between an affiliated mesh STA and a mesh STA case, wherein in case the peering takes place between mesh MLDs, the additional parameter is included in the set of primitives, and in case the peering takes place between an affiliated mesh STA and a mesh STA, the additional parameter is not included in the set of primitives, wherein the additional parameter is a conditional parameter; or an additional parameter is selected, wherein the value of the additional parameter is used to distinguish peering between a mesh MLDs case and peering between an affiliated mesh STA and a mesh STA case, wherein if the value of the additional parameter is 1 the peering takes place between mesh MLDs, and if the value of the additional parameter is 0 the peering takes place peering between mesh MLDs and peering between an affiliated mesh STA and a mesh STA, wherein the additional parameter is a fixed parameter; or the presence of a multi-link element as a parameter in the set of primitives and in the corresponding peering frames is used to indicate peering between mesh MLDs.

10. The method according to claim 9, wherein the additional parameter is referred to as MeshMACAddress parameter.

11. The method according to claim 9 or 10, wherein in case the additional parameter is selected to distinguish a case of peering between peer mesh MLDs, and a case of peering between an affiliated mesh STA and a mesh STA, discovering, by any peer mesh MLD, or a peer mesh STA, wherein: if a solicited peer mesh MLD is discovered, issuing, by the initiating peer mesh MLD, a request primitive with the additional parameter set to the initiating peer mesh MLD MAC Address and setting a parameter of the peer MAC address to the MAC Address of the solicited peer mesh MLD, wherein the frame body of the Mesh Peering Open frame includes the MLE;if a peer mesh STA is discovered, issuing, by the initiating STA affiliated with a peer mesh MLD a request primitive including no additional parameter and setting a parameter of the peer MAC address to the MAC Address of the solicited mesh STA, wherein the frame body of the Mesh Peering Open frame does not include the MLE.12 The method according to claim 11, wherein the request primitive is referred to as MESHPEERINGMANAGEMENT.request.

13. The method according to claim 11 to 12, wherein the process for the solicited peer mesh MLD responding to a mesh peering request comprises: receiving a Mesh Peering Open frame through a STA affiliated with the peer mesh MLD, the SME of the peer mesh MLD generates an indication primitive, wherein: if the MLE is included in the Mesh Peering Open frame, the additional parameter is set to the initiating mesh MLD MAC Address; if the additional parameter is present in the received indication primitive, issuing, by the SME of the solicited peer mesh MLD, response primitive with the additional parameter set to the solicited peer mesh MLD MAC Address and the parameter of the peer MAC address set to the MAC Address of the initiating peer mesh MLD; wherein an MLE is included in a confirm primitive and is transmitted in the Mesh Peering Confirm frame; if the additional parameter is not present in the received indication primitive, issuing, by the SME of the second peer mesh MLD response primitive with no additional parameter and the parameter of the peer MAC address set to the MAC Address of the peer mesh STA, wherein an MLE is not included in the confirm primitive and is not transmitted in the Mesh Peering Confirm frame.

14. The method according to claim 13, wherein the indication primitive is referred to as MESHPEERINGMANAGEMENT. indication primitive; and / or wherein the response primitive is referred to as MESHPEERINGMANAGEMENT.response primitive; and / or wherein the confirm primitive is referred to as MESHPEERINGMANAGEMENT. confirm primitive.

15. The method according to any one of claims 2 to 14, wherein in case peering is successfully performed between an affiliated mesh STA and a mesh STA, the method further comprises establishing a security association by the peer mesh MLD with the mesh STA.

16. The method according to claim 15, establishing the security association further comprises the affiliated mesh STA establishing a security association with the mesh STA including both a pairwise key and group key.

17. The method according to any one of claims 3 to 16, wherein in case peering is successfully performed between the peer mesh MLDs, the connection is established between the peer mesh MLDs and data is transmitted across the links within the security association; wherein these links are referred to as setup links, wherein transmitting data across setup links comprises cryptographically encapsulating data frames at upper MAC layer.

18. The method according to claim 17, wherein cryptographically encapsulating data frames at the upper MAC comprises calculating Additional Authentication Data, AAD, using the peer mesh MLD MAC address of the respective peer mesh MLDs.

19. The method according to claim 18, wherein group key management and group addressed cryptographic encapsulation is performed at the respective peer mesh MLDs.

20. The method according to any one of claims 2 to 19, further comprising: in case peering is performed between the peer mesh MLDs, the respective peer mesh MLD MAC address is used to define a relay point for the next hop; in case peering is performed between an affiliated mesh STA and a mesh STA, with respect to the mesh STA, the MAC address of the mesh STA affiliated with the peer mesh MLD is used to define the relay point for the next hop, wherein the MAC address of the peer mesh MLD will be automatically defined as the next relay hop for each of the mesh STAs affiliated with that peer mesh MLD.

21. The method according to claim 20, wherein if two or more setup links are negotiated during the peering procedure between mesh MLDs, the transmitting peer mesh MLD selects which setup link, is used to send traffic on a frame by frame basis.

22. A mesh device in a wireless mesh network, wherein: the mesh device is configured to peer with a second mesh device, wherein the mesh device is either a first peer mesh multi-link device, MLD, and the second mesh device is a second peer mesh MLD wherein each of the first and the second peer mesh MLDs comprise one or more affiliated mesh stations, STAs; or the mesh device is a mesh STA affiliated with a mesh MLD, and the second mesh device is a mesh STA; wherein the mesh device is configured to initiate peering after a discovery procedure is completed between the first mesh device and the second mesh device.

23. The mesh device e method according to claim 22, wherein in case the second mesh device is a mesh STA, mesh data is exchanged between the mesh STA and an affiliated mesh STA of the first peer mesh MLD.

24. The mesh device according to claim 22, wherein the peering procedure is unidirectional; wherein in case peering takes place between the first peer mesh MLD and the second peer mesh MLD, the peering comprises: the first peer mesh MLD, being an initiating peer mesh MLD, is configured to transmit to the second peer mesh MLD, being a solicited peer mesh MLD, a frame for opening the mesh peering, Mesh Peering Open frame; the initiating peer mesh MLD, after the transmission of the Mesh Peering Open frame, is configured to receive a frame for confirming the mesh peering, a Mesh Peering Confirm frame, transmitted by the solicited peer mesh MLD to complete the peering.

25. The mesh device according to claim 24, wherein the initiating peer mesh MLD is configured to transmit the Mesh Peering Open frame through one of its affiliated STAs, the solicited peer mesh MLD is configured to receive the Mesh Peering Open frame through one of its affiliated STAs, and wherein the solicited peer mesh MLD is configured to transmit the Mesh Peering Confirm frame through the same affiliated STA.

26. The mesh device according to claim 24 or 25, wherein the Mesh Peering Open frame includes a multi-link element, MLE, wherein the multi-link element includes a set of links requested to be setup for use for mesh data communication between the initiating peer mesh MLD and the solicited peer mesh MLD.

27. The mesh device according to claim 26, wherein the Mesh Peering Confirm frame includes a multi-link element, MLE, wherein the multi-link element includes a subset of the links requested by the initiating peer mesh MLD and are accepted by the solicited peer mesh MLD for use for mesh data communication.

28. The mesh device according to claim 26 or 27, wherein the set of links, requested by the initiating peer mesh MLD and accepted by the solicited peer mesh MLD, is unidirectional to be used by the peer mesh MLD that has initiated the peering, when it initiates the transmission of frames to the peer mesh MLD that have been solicited for a peering.

29. The mesh device according to any one of claims 24 to 28, wherein any of the peer mesh MLDs are configured to transmit a frame for closing the mesh peering, Mesh Peering Close frame, on any of the setup links between transmitting mesh MLD and the peer mesh MLD, for terminating the data exchange between the initiating peer mesh MLD and the solicited peer mesh MLD.

30. The mesh device according to any one of claims 23 to 29, wherein a single set of primitives is used by the Station Management Entity, SME, of the MLD for all mesh peering related operations for the transmission of Mesh Peering Open, Mesh Peering Confirm, and Mesh Peering Close frames, wherein in order to support mesh multi-link operation, MLO: an additional parameter is selected to distinguish peering between a mesh MLDs case and peering between an affiliated mesh STA and a mesh STA case, wherein in case the peering takes place between mesh MLDs, the additional parameter is included in the set of primitives, and in case the peering takes place between an affiliated mesh STA and a mesh STA, the additional parameter is not included in the set of primitives, wherein the additional parameter is a conditional parameter; or an additional parameter is selected, wherein the value of the additional parameter is used to distinguish peering between a mesh MLDs case and peering between an affiliated mesh STA and a mesh STA case, wherein if the value of the additional parameter is 1 the peering takes place between mesh MLDs, and if the value of the additional parameter is 0 the peering takes place peering between mesh MLDs and peering between an affiliated mesh STA and a mesh STA, wherein the additional parameter is a fixed parameter; orthe presence of a multi-link element as a parameter in the set of primitives and in the corresponding peering frames is used to indicate peering between mesh MLDs.

31. The mesh device according to claim 30, wherein the additional parameter is referred to as MeshMACAddress parameter.

32. The mesh device according to claim 30 or 31, wherein in case an additional parameter is selected to distinguish a case of peering between peer mesh MLDs, and a case of peering between an affiliated mesh STA and a mesh STA, the mesh device being any of peer mesh MLD, or peer mesh STA is configured to start discovering, wherein: if a solicited peer mesh MLD is discovered, the initiating peer mesh MLD is configured to issue a request primitive with the additional parameter set to the initiating peer mesh MLD MAC Address and to set a parameter of a peer MAC address to the MAC Address of the solicited peer mesh MLD, wherein the frame body of the Mesh Peering Open frame includes the MLE; if a peer mesh STA is discovered, issuing, the initiating STA affiliated with a peer mesh MLD is configured to issue a request primitive including no additional parameter and to set the parameter of the peer MAC address parameter to the MAC Address of the solicited mesh STA, wherein the frame body of the Mesh Peering Open frame does not include the MLE.

33. The mesh device according to claim 32 wherein the request primitive is referred to as MESHPEERINGMANAGEMENT.request.

34. The mesh device according to claim 30 to 33, wherein the process for the solicited peer mesh MLD responding to a mesh peering request comprises: receiving a Mesh Peering Open frame through a STA affiliated with the peer mesh MLD, the SME of the peer mesh MLD generates an indication primitive, wherein: if the MLE is included in the Mesh Peering Open frame, the additional parameter is set to the initiating mesh MLD MAC Address; if the additional parameter is present in the received indication primitive, issuing, by the SME of the solicited peer mesh MLD, a response primitive with the additional parameter set to the solicited peer mesh MLD MAC Address and the parameter of the peer MAC address set to the MAC Address of the initiating peer mesh MLD; wherein an MLE is included in a confirm primitive and is transmitted in the Mesh Peering Confirm frame; if the additional parameter is not present in the received indication primitive, issuing, by the SME of the second peer mesh MLD primitive response primitive with no additional parameter and the parameter of the peer MAC address set to the MAC Address of the peer mesh STA, wherein an MLE is not included in a confirm primitive and is not transmitted in the Mesh Peering Confirm frame.35 The mesh device according to claim 34 wherein the indication primitive is referred to as MESHPEERINGMANAGEMENT. indication primitive; and / or wherein the response primitive is referred to as MESHPEERINGMANAGEMENT.response primitive; and / or wherein the confirm primitive is referred to as MESHPEERINGMANAGEMENT. confirm primitive.

36. The mesh device according to any one of claims 23 to 35, wherein in case peering is successfully performed between an affiliated mesh STA and a mesh STA, the mesh device is further configured to establish a security association by the peer mesh MLD with the mesh STA.37 The mesh device according to claim 36, wherein establishing the security association further comprises the affiliated mesh STA establishing a security association with the mesh STA including both a pairwise key and group key.

38. The mesh device according to any one of claims 24 to 35, wherein in case peering is successfully performed between the peer mesh MLDs, the connection is established between the peer mesh MLDs and data is transmitted across the links within the security association. These links are referred to as setup links, wherein transmitting data across setup links comprises cryptographically encapsulating data frames at upper MAC layer.

39. The mesh device according to claim 38, wherein cryptographically encapsulating data frames at the upper MAC comprises calculating Additional Authentication Data, AAD, using the peer mesh MLD MAC address of the respective peer mesh MLDs.

40. The mesh device according to claim 39, wherein group key management and group addressed cryptographic encapsulation is performed at the respective peer mesh MLDs.

41. The mesh device according to any one of claims 23 to 40, further comprising: in case peering is performed between the peer mesh MLDs, the respective peer mesh MLD MAC address is used to define a relay point for the next hop; in case peering is performed between an affiliated mesh STA and a mesh STA, with respect to the mesh STA, the MAC address of the mesh STA affiliated with the peer mesh MLD is used to define the relay point for the next hop, wherein the MAC address of the peer mesh MLD will be automatically defined as the next relay hop for each of the mesh STAs affiliated with that peer mesh MLD.

42. The mesh device according to claim 41, wherein if two or more setup links are negotiated during the peering procedure between mesh MLDs, the transmitting peer mesh MLD selects which setup link, is used to send traffic on a frame by frame basis.

43. A computer program product comprising program code for performing the method according to any one of the preceding claims 1 to 21 when executed on a computer or a processor.

44. A non-transitory computer-readable medium carrying a program code which, when executed by a computer device, causes the computer device to perform the method of any one of claims 1 to 21.

Images