Method for managing nodes of a wireless communication network, method for processing a request to modify a configuration of a connection between the nodes, devices and corresponding computer programs

Abstract

The invention relates to a method for managing a configuration of a plurality of nodes of a wireless communication network controlled by a controller node), said method comprising the steps of: obtaining (30) information relating to a control action on one of said frequency bands, programmed to be executed by at least one of said nodes, called executing node; transmitting (34), to at least one node, called impacted node, of the plurality of nodes, comprising said at least one executing node, said impacted node having established at least one multi-link connection with at least one other node of said plurality of nodes, a request for modification of the configuration of said at least one connection, for a link of the multi-link connection using the frequency band, said configuration modification being a function of said control action;and upon receipt (35), from said at least one impacted node, of a confirmation of modification of configuration of said at least one connection, transmission (36) to said controller node of information indicating that said control action programmed on said frequency band is ready to be executed. Figure 3;

Description

Title of the invention: Method for managing nodes of a wireless communication network, method for processing a request to modify a configuration of a connection between the nodes, devices and corresponding computer programs Technical field

[0001] The invention relates to the technical field of wireless communications networks and, more precisely, to access equipment, or access points, to wireless communications networks, which are connected to each other by a plurality of links implementing distinct frequency bands. It relates in particular to the adaptation of a configuration of a connection between two access equipment when a control action likely to disrupt communications on one or more of these frequency bands via this connection must be executed. State of the prior art

[0002] The IEEE802.1 Ibe wireless communication standard, from the IEEE802.il family, standardized by the IEEE and adopted by the Wi-Fi alliance under the name Wi-Fi 7, is known as a solution for connecting devices to each other on several different frequency bands at the same time, which are used together to transmit and receive data between these devices.

[0003] We also know of the standard called EasyMesh, also standardized by the Wi-Fi alliance, a solution for deploying and managing a wireless mesh network connecting Wi-Fi access point devices potentially produced by different manufacturers. It is based on a set of transactions between these access points forming nodes of this mesh network, typically a controller node device and agent node devices. According to this solution, the agent nodes register with the network controller node in order to be configured by the latter. The controller node benefits from a global vision of the network, in that it knows both the configuration and the state of each agent of the network.

[0004] In the context of managing such a wireless mesh network, the controller node is regularly required to trigger the execution of various control procedures or actions at the level of one or more agent nodes and more precisely of one or more of the frequency bands that they use to communicate with each other. They act on the node and on the connections that it has established with other nodes.

[0005] Such actions are therefore likely to disrupt communications between node equipment, at varying levels, in a more or less impactful manner. By way of example and in a non-exhaustive manner, we cite:

[0006] - a procedure for analyzing or scanning a frequency band or Wi-Fi Scan, which is an operation performed by a device to search for and detect available Wi-Fi networks in its environment. When a device such as a smartphone, laptop, or tablet performs a Wi-Fi scan, it sends radio signals on the frequency band to detect nearby Wi-Fi networks. These radio signals allow the device to locate active Wi-Fi networks and retrieve information about these networks, such as their name or Service Set Identifier (SSID), their signal strength, their channel, their security mode, etc. It is understood that during this frequency band scanning operation, the device cannot transmit or receive data on this frequency band. For a complete scan on a fairly wide frequency band, the scan time can last several seconds.

[0007] - a procedure for verifying the availability of a Wi-Fi or Wi-Fi CAC channel (from the English "Channel Availability Check"), which is a specific feature of the Wi-Fi protocol, designed to help regulate competitive access to this transmission channel. By implementing this procedure, a Wi-Fi device can detect and monitor traffic on the channel in question, before transmitting data. This allows the device to ensure that there are no other transmissions in progress that could cause data collisions and disrupt communication. The Wi-Fi CAC procedure is particularly important in environments where multiple Wi-Fi devices operate in a confined space, such as in enterprise wireless networks or densely populated areas. It helps avoid interference and maintain optimal network performance. A particular use of this Wi-Fi CAC procedure is in preparation for a channel change to a radar-protected channel.According to an official regulation concerning a part of the radar frequency band around 5GHz, any device wishing to use this part of the protected frequency band is required to first passively listen for any potential radar signals for at least one minute before emitting its own radio signals, i.e. to implement the Wi-Fi CAC procedure. It cannot therefore transmit or receive during this period of time.

[0008] - a Wi-Fi detection procedure (in English “Wi-Fi Sensing”), which consists of to transmit continuously for a period of time to perform variation analysis upon receiving data packets. This action uses standard Wi-Fi packets, but with a high sending frequency. In theory, it does not directly prevent the transmission or reception of other Wi-Fi data packets by the device that performs the procedure, but because it saturates the radio channel, it is likely to disrupt the transmission or reception of certain types of data streams, in particular those associated with high latency and packet loss constraints, such as a real-time data stream (in English, "live"), such as video or voice. In addition, this Wi-Fi Sensing procedure involves not only the agent node that triggers this action by transmitting data to another node on a given link of the connection it has established with it, but also this other node, which must respond to the data it has received from the agent node. The Wi-Fi sensing action therefore requests two nodes of the wireless network simultaneously.

[0009] A disadvantage of these control actions on the node access points of the mesh network is that they disrupt communications via the connections established between them, to varying degrees, with a more or less strong impact on the quality of service experienced by the users of the corresponding wireless communication networks. Summary

[0010] The invention improves the situation. In particular, the invention aims at a solution for adapting upstream the configuration of the agent nodes and their connections with other agent nodes, likely to be impacted by the execution of one of these control actions, in order to avoid or at least limit the disturbances on their communications with these other nodes of the wireless communication network.

[0011] According to a first aspect, a method for managing a configuration of a plurality of nodes of a wireless communication network controlled by a controller node is proposed, said nodes of the plurality of nodes being configured to establish between them connections, called multi-links, comprising at least two links using at least two distinct frequency bands, said method comprising the steps of: - obtaining information relating to a control action on one of said frequency bands, programmed to be executed by at least one said node, called executing node; - transmission, to at least one node, called the impacted node, of the plurality of nodes, comprising said at least one executing node, said impacted node having established at least one multi-link connection with at least one other node of said plurality of nodes, of which at least one link, called the impacted link, uses said frequency band on which the control action is programmed, of a request for modification of the configuration of said at least one connection, for the impacted link, said modification of configuration being a function of said control action; and - upon receipt, from said at least one impacted node, of a confirmation of modification of the configuration of said at least one connection, transmission to said controller node of information indicating that said programmed control action on said frequency band is ready to be executed.

[0012] The proposed solution is based on a completely new and inventive approach to the control of the agent nodes of a wireless network by a controller node, which consists of anticipating the disturbances caused by the execution of a control action on one or more nodes of the wireless network, by ordering them to modify the configuration of their multi-link connections which will be impacted by this control action, before the execution of this control action. An advantage is to exploit the knowledge natively available to the controller node of the connections established by each of the nodes of the wireless network and their state to coordinate a modification of the configurations of their multi-link connections, before triggering the execution of the control action in question. The ordered configuration modification depends on the programmed control action and the nodes to which it applies depends on the configuration of the wireless network.

[0013] In this way, disruptions to communications between the agent nodes in question and other nodes are avoided, or even minimized.

[0014] According to one or more embodiments, the method is implemented by the controller node. Alternatively, it is implemented by a management device which can be integrated into the controller node or connected to it by communication means.

[0015] The invention applies to any wireless communication network whose nodes are access points which communicate with each other using (simultaneously) several links implementing distinct frequency bands. For example, the wireless network is a mesh network.

[0016] It applies in particular, but not limited to, a plurality of access points to Wi-Fi type wireless communication networks implementing the IEEE802.1 Ibe standard, of the IEEE802.11 family, or Wi-Fi 7 or one of its later versions, connected together to form nodes of a mesh network controlled by a controller node, in accordance with the standard called EasyMesh, in its current version or one of its later versions.

[0017] According to one or more embodiments, the method further comprises the steps of:

[0018] - obtaining a report of execution of said control action (CA) on said frequency band, received by said controller node from said at least one executing node, and

[0019] - transmission, to said at least one impacted node, of a request for restoring the configuration of said at least one connection.

[0020] Once the control action has been executed, the controller node commands the said at least one impacted node to reestablish the configurations of its connections. In this way, it restores its connections to the state they were in before the executing node performed the control action.

[0021] According to one or more embodiments, the request for modification of the configuration of said at least one multi-link connection comprises a command for deleting an authorization for transmission and reception of data on said impacted link for at least one type of data flow.

[0022] The configuration modification ordered by the controller node to the agent nodes depends on the nature of the control action and can range from a suppression of an authorization to transmit and receive data on the frequency band concerned by the control action for at least one given type of flow to a total suppression, regardless of the type of flow. In the case of such a total or partial suppression, the other links of the connection will be used to transmit the data of a flow of said at least one type concerned. An advantage of this modification of the configuration of the connections of the agent nodes of the wireless communication network is that it is adapted in a proportionate manner to the control action.

[0023] According to one or more embodiments, the method comprises obtaining information relating to a type of configuration modification, at least as a function of the information relating to the control action and, when the information relating to a type of configuration modification comprises an interruption of the data traffic on said impacted link, said command to remove an authorization to transmit and receive data on said link concerns all the types of data flows of the multi-link connection and, when the information relating to a type of configuration modification comprises a reduction of the data traffic on said impacted link, said removal of an authorization to transmit and receive data on said link does not concern all the types of data flows.

[0024] For example, for a control action of the scanning type of a given frequency band of the verification type of availability of a given frequency band, the configuration modification consists of completely interrupting the traffic on the impacted link. On the other hand, for a control action of the variation analysis type upon reception of data on a given frequency band (Wi-Fi sensing), the data traffic can only be reduced, by eliminating the use of the impacted link for certain types of data flows.

[0025] For example, the type of flow concerned by this deletion is a type of flow associated with strong latency constraints, for example a real-time flow of the video or voice type.

[0026] According to one or more embodiments, the method further comprises obtaining a list of said nodes impacted by said control action, said list comprising said at least one executing node and at least one other node connected to said at least node equipment by a multi-link connection comprising said impacted link, and in that the request for notification of modification of configuration of said link is sent to the impacted nodes of said list.

[0027] An advantage of the proposed solution is that it relies on knowledge of the impact of the programmed control action on the nodes of the wireless communication network, to coordinate these nodes so that they no longer transmit data on the link using the frequency band which is the subject of the control action or only the types of flows which support the disturbance generated.

[0028] According to one or more embodiments, the method further comprises the step of obtaining, from the plurality of nodes of said network, information relating to a radio signal level received from neighboring nodes, and in that the list of nodes impacted by said programmed control action is determined at least from said received information and a minimum threshold of radio signal level received.

[0029] For example, the controller node commands the plurality of agent nodes of the wireless communication network to implement a neighbor reporting procedure, such as for example defined by the IEEE 802.11k standard. Such a procedure consists of an agent node listening to its neighbors and, for each detected radio signal, determining information on the level of the received radio signal. The agent node compiles the information into a structured neighbor report which it transmits to the controller node.

[0030] The controller node then uses it to evaluate, for each node of the mesh network, from the radio signal level information received from the plurality of nodes and the minimum received signal level threshold, a range measurement. From this range measurement, it can determine which node is "visible" to which other node and consequently, which nodes of the mesh network will be impacted by the execution of a control action by the executing node.

[0031] In this way, the controller node establishes in a simple and efficient manner an impact study of the upcoming control action.

[0032] According to a second aspect, a method for processing a request to modify a configuration of a node to a wireless communication network is proposed, said wireless communication network comprising a plurality of nodes, said nodes of the plurality of nodes being configured to establish between them connections, called multi-links, comprising at least two links using at least two distinct frequency bands, said wireless communication network being controlled by a controller node, said method comprising the steps of: - obtaining a request to modify the configuration of one said at least one multi-link connection, established by the node with at least one other node of said wireless communication network, said request having been received by said node from a controller node of said wireless mesh network, said request comprising a command to remove an authorization to transmit and receive data on the link using a given frequency band, for at least one type of data flow, - triggering the transmission by said node to said at least one other node of a first request for renegotiation of said connection, implementing said command for deleting an authorization for transmission and reception of data on said link for said at least one connection, for the at least one type of data flow, and - following the renegotiation of said connection, triggering the transmission by said node of a message comprising a report of execution of the configuration modification to the controller node.

[0033] With the proposed solution, any node of the wireless network is configured to reconfigure its connections with other access equipment, upon request from and according to the terms prescribed by the controller node. In this way, the latter can trigger this reconfiguration upstream of the execution of a future control action on this node or on another node of the wireless network to which the node is connected.

[0034] According to one or more embodiments, the method further comprises the steps of: - obtaining a configuration restoration request, received by said node from the controller node, said request comprising a command to add an authorization for transmission and reception of data on said link for said at least one connection, for said at least one type of flow, - triggering the transmission by said node, to the at least one other node, of a second request for renegotiation of said at least one connection, implementing the command for adding an authorization for transmission and reception of data on said link for said at least one connection, for said at least one type of flow, and - triggering the transmission by said node of a message comprising a report of execution of the reestablishment of the configuration of said at least one connection.

[0035] The restoration of the initial configuration is implemented in a similar manner, which allows the node to recover the state of its connections with other access points before the reconfiguration. Advantageously, this configuration restoration procedure takes place following the execution of the control action by the node or by another node to which it is connected.

[0036] According to one or more embodiments, when said node is connected to a plurality of nodes by connections implementing a link using the given frequency band, said configuration modification request message is sent to said plurality of other nodes.

[0037] According to one or more embodiments, the first, respectively second request for renegotiation of said at least one connection comprises information indicating a list of links authorized for said at least one connection.

[0038] In this way, said list included in the first, respectively the second request replaces the list of authorized links which was previously applicable. Thus, it is sufficient to remove the link to be deleted for said at least one data flow from the list of the first request and to reintegrate it into the list of the second request.

[0039] According to a third aspect, a device for managing a configuration of a plurality of nodes of a wireless communication network controlled by a controller node is proposed, said nodes of the plurality of nodes being configured to establish between them connections, called multi-links, comprising at least two links using at least two distinct frequency bands, said device being configured to: - obtain information relating to a control action on one of said frequency bands, said control action being programmed to be executed by at least one node of said network, called the executing node; - transmitting to at least one node, called the impacted node, of the plurality of nodes, comprising said at least one executing node, said impacted node having established at least one connection with at least one other node of said plurality of nodes, of which at least one link, called the impacted link, uses said frequency band on which the control action is programmed, a request for modification of the configuration of said at least one connection, for the impacted link, said modification of configuration being a function of said control action; and - upon receipt, from said at least one impacted node, of a confirmation of modification of the configuration of said at least one connection, transmit to said controller node information indicating that said control action programmed on said frequency band is ready to be executed.

[0040] According to at least one embodiment, said device comprises at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the execution of said device.

[0041] According to at least one embodiment, such a device implements the management method according to the first aspect, in its different embodiments.

[0042] According to a fourth aspect, a device for processing a request to modify a configuration of a node of a wireless communication network comprising a plurality of nodes connected to each other by connections, called multi-links, comprising at least two links using distinct frequency bands, said network being controlled by a controller node, said node having established at least one connection with another node of said network, said device being configured to: - obtaining a request for modification of configuration of at least one multi-link connection, received by said node, for the link of said plurality of links using a given frequency band from a controller node of said wireless mesh network, said request comprising a command for removing an authorization for transmission and reception of data on said link for said at least one connection, for at least one type of data flow, - triggering a transmission by said node to said at least one other node of a first request for renegotiation of said connection, implementing said command for deleting an authorization for transmission and reception of data on said link for said at least one connection, for at least one type of data flow, and - following the renegotiation of said connection, trigger a transmission by said node of a message comprising a report of execution of the configuration modification to the controller node.

[0043] According to at least one embodiment, said aforementioned processing device comprises at least one processor and at least one memory comprising a computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the execution of said device.

[0044] According to at least one embodiment, such a device implements the treatment method according to the second aspect, in its different embodiments.

[0045] According to a fifth aspect, access equipment to a wireless communication network forming a node of a wireless communication network comprising a plurality of nodes is proposed, said nodes of the plurality of nodes being configured to establish between them connections, called multi-links, comprising at least two links using distinct frequency bands, said node having established at least one said multi-link connection, comprising at least two links using the at least two distinct frequency bands, the access equipment comprising a processing device according to the fourth aspect.

[0046] According to one or more embodiments, the access equipment according to is said to be an executing node and further configured to: - receive, from a controller node of said wireless communication network, a command to execute a control action on one of said frequency bands, - following execution of the control action, issue an action execution report to the controller node equipment.

[0047] According to a sixth aspect, a wireless communication network comprising a plurality of nodes is proposed, said nodes being access equipment according to the fifth aspect and at least one management device according to the third aspect.

[0048] The management device may be embedded in a control node device. The controller node may be one of the access node devices of the network. Alternatively, it may be distributed in the plurality of access devices forming the nodes of the wireless communication network.

[0049] The wireless communication network, the access equipment and the management device have the same advantages as the aforementioned management method.

[0050] According to a seventh aspect, a computer program is provided, comprising instructions for executing a method according to the first aspect, when said program is executed by a computer.

[0051] According to an eighth aspect, a non-volatile, computer-readable recording medium is provided, on which the computer program according to the seventh aspect is recorded.

[0052] According to a ninth aspect, a computer program comprising instructions for executing a method according to the second aspect, when said program is executed by a computer.

[0053] According to a tenth aspect, a non-volatile computer-readable recording medium is provided, on which the computer program according to the ninth aspect is recorded. Brief description of the drawings

[0054] Other characteristics and advantages will appear during the reading of the detailed description which follows for the understanding of which one will refer to the attached drawings among which:

[0055] [Fig.l] schematically illustrates a device for managing a plurality of nodes of a wireless network and devices for processing a request to modify a configuration of a multi-link connection between nodes of a wireless network, said nodes being equipment for accessing wireless communication networks, according to a particular non-limiting example embodiment;

[0056] [Fig.2] schematically illustrates an example of paths taken by flows of data packets exchanged via a multi-link connection between two nodes of the wireless network;

[0057] [Fig.3] presents in the form of a flowchart the steps of a method for managing a plurality of nodes of a wireless network, according to a particular non-limiting exemplary embodiment;

[0058] [Fig.4] details in the form of a flowchart the obtaining of a list of the nodes of the wireless network impacted by a control action programmed to be executed by a node of the wireless network, according to a particular non-limiting exemplary embodiment;

[0059] [Fig.5] presents in the form of a flowchart the steps of a method for processing a request to modify a configuration of a multi-link connection established by a node of the wireless network with another node of this network, according to a particular non-limiting exemplary embodiment;

[0060] [Fig.6] schematically illustrates an example of renegotiation messages for a multi-link connection between two nodes of the wireless network, according to one embodiment;

[0061] [Fig.7] presents the message flows exchanged between a controller node and a node of the wireless network to modify the configuration of a multi-link connection established by this node, before the execution of a programmed control action of the Wi-Fi Scan type, according to a particular non-limiting example embodiment;

[0062] [Fig.8] schematically illustrates an example of paths taken by flows of data packets exchanged via multi-link connections between nodes of the wireless network, after a modification of their configuration before the execution of a Wi-Fi Scan type control action on a given frequency band, according to a particular non-limiting example embodiment;

[0063] [Fig.9] schematically illustrates areas of impact of nodes on other nodes of a wireless network, according to a particular non-limiting exemplary embodiment;

[0064] [Fig. 10] presents the message flows exchanged between a controller node and agent nodes of a wireless network to modify the configurations of their respective multi-link connections, before the execution of a programmed control action of the Wi-Fi Sensing type, according to a particular non-limiting exemplary embodiment;

[0065] [Fig. 11] schematically illustrates an example of paths taken by flows of data packets exchanged via the multi-link connections between the nodes of the mesh network, after a modification of their configuration before the execution of a WiF6 Sensing type control action on a given frequency band, according to a particular non-limiting example embodiment;

[0066] [Fig. 12A] presents as an example a table of values ​​of an information element (TID - To-Link Mapping) indicating a list of authorized links for a multi-link connection;

[0067] [Fig.l2B] schematically illustrates an example of a nominal configuration of a multi-link connection, according to which all types of traffic are allowed on all links;

[0068] [Fig.l2C] schematically illustrates an example of a modified configuration of a multi-link connection, according to which certain types of traffic are not allowed on a given link;

[0069] [Fig. 13] schematically illustrates an example of hardware structure of a device for controlling, or modifying, a configuration, according to one or more embodiments of the invention. Description of the embodiments

[0070] In the following description, identical, similar or analogous elements will be designated by the same reference numerals. Unless otherwise indicated, the diagrams are not necessarily to scale.

[0071] The block diagrams, flowcharts and message sequence diagrams in the figures illustrate the architecture, functionality and operation of systems, devices, methods and computer program products according to one or more exemplary embodiments. Each block of a block diagram or each phase of a flowchart may represent a module or a portion of software code comprising instructions for implementing one or more functions. According to certain implementations, the order of the blocks or phases may be changed, or the corresponding functions may be implemented in parallel.

[0072] The exemplary embodiments which will now be described are placed, in a non-limiting manner, in the context of networks conforming to the family of 802.11 standards of the Institute of Electrical and Electronics Engineers "IEEE", or so-called 'Wi-Fi' type networks. Exemplary embodiments may be placed, for example, in the context of the IEEE 802.1 Ibe amendment, in its D4.0 version or its D5.0 version, or in its later versions or its final version. Other exemplary embodiments may also be placed, for example, in the context of a version of the IEEE 802.11 standard or an amendment to this 802.11 standard incorporating the IEEE 802.1 Ibe amendment, such as, for example, the IEEE 802.1 Ibf D3.0 amendment or the IEEE 802.11bn amendment. They are suitable for both home and business wireless networks.

[0073] In the following, we consider in particular access equipment or access points (in English, “Access Point”), that is to say a hardware device which allows to stations, i.e. devices, such as user terminals, such as a laptop, a smartphone, a tablet, etc. or connected objects or loT (in English, "Internet of Thing"), to connect to the local communication network or LAN (for "Local Access Network") in English), via a wireless connection. Such an access point creates a wireless local network in a given area, providing radio coverage for devices located nearby. It is generally connected to a wide communication network or WAN (from the English, "Wide Access Network"), for example wired, and acts as a gateway (in English, "gateway") between the devices and the wired network, allowing them to communicate with other devices connected to the wide network and to access the Internet if the access point is connected to an Internet router.

[0074] More specifically, in relation to [Fig.l], we consider a plurality of access devices connected together to form nodes of a wireless network MN. In this example, the network has a mesh structure and forms a mesh network. Of course, other structures can be envisaged, such as for example a star organization.

[0075] In this example, an access device A to a wireless local area network LANA is connected by a multi-link MLO (Multi Link Operations) CAB connection to an access device B to a local area network LANB. This CAB connection comprises three links L1{A,B], L2{A,B], L3{A,B] each using one of the three distinct frequency bands defined by the Wi-Fi 6E protocols incorporating the IEEE 802.1 lax-2021 amendment and Wi-Fi 7 incorporating the IEEE 802.11be amendment, respectively 2.4GHz, 5GHz and 6GHz.

[0076] The IEEE 802.1 Ibe variant, or also called and referred to by this acronym below, Wi-Fi7, defines the concept of multi-link connection and messages allowing to establish and manage such a connection. The Wi-Fi7 standard makes it possible to establish a connection between two devices on a given frequency band, then to negotiate transmission modes on the other frequency bands common between the two devices so that they can transmit and receive data on the different frequency bands simultaneously. It also makes it possible to negotiate in real time the frequency bands or links to be used to transmit and receive data via this connection.

[0077] In the example of [Fig.l], the access equipment B is itself connected to an access equipment C to a local network LANC by a multi-link connection CBC and to an access equipment D to a local network LAND by a multi-link connection CBD. Finally, the access equipment C is connected by a multi-link connection CDE to an access equipment E to a local network LANE.

[0078] Nodes C and D are connected to node B and have each negotiated a multi-link connection on the 3 frequency bands which are respectively denoted L1{B,C], L2{B,C], L3{B,C] and L1{B,D], L2{B,D], L3{B,D}.

[0079] As a purely illustrative example, a user terminal UA connected to the local network LANA, a user terminal UB connected to the local network LANB, a user terminal UC connected to the local network LANC, a user terminal UD connected to the local network LAND and a user terminal UE connected to the local network LANE are shown. The user terminals UA-UE (or stations or STAs in the terminology of one of the standards of the IEEE 802.11 family) are for example a smartphone, a computer, a tablet or even a connected object.

[0080] The wireless mesh network MN is for example constructed in accordance with the EasyMesh standard which describes mechanisms and messages allowing its nodes to coordinate with each other. More precisely, the mesh network MN is constructed through the configuration of a controller node (not shown in [Fig.l]) configured to control the configuration of the AE nodes of the wireless network MN. It should be noted that the controller node is generally an access device in the same way as the other AE nodes.

[0081] Thus, in the MN mesh network of [Fig.l], each AE node implements the Wi-Fi7 standard on the three frequency bands 2.4GHz, 5GHz and 6GHz as well as the EasyMesh standard (for example versions or revisions 5.0, and later ones compatible with the previous ones) to build and manage the MN mesh network. For example, the EasyMesh standard is implemented on each of the nodes of the mesh network using a software program, called an agent.

[0082] In relation to [Fig.2], nodes C and D communicate with node A through node B on the 3 links of their respective connections. In [Fig.2], the packet flows exchanged on different paths between the AE nodes are represented with arrows. The solid line arrows designate the L1 links using the 2.4GHz frequency band, those in large dotted lines the L2 links using the 5GHz frequency band and those in small dotted lines the L3 links using the 6GHz frequency band.

[0083] The flows fl of data packets exchanged between A and C through the link L1 take the following path:

[0084] AC(fl): L1{A,B}+ L1{B,C}.

[0085] Similarly, node E communicates with node A through nodes B and C. Thus, the set of flows fl, f2, f3 is written as follows: - Between A and C: AC (fl): L1{A,B] + L1{B,C]

[0086] AC (f2): L2{A,B] + L2{B,C]

[0087] AC (f3): L3{A,B] + L3{B,C] - Between A and D: AD (fl): L1{A,B]+ L1{B,D]

[0088] AD (f2): L2{A,B] + L2{B,D]

[0089] AD(f3): L3{A,B}(3) + L3{B,D] - Between A and E: AE (fl): L1{A,B] + L1{B,C] + L1{C,E}

[0090] AAE (f2): L2{A,B} + L2{B,C] + L2{C,E]

[0091] AE (f3): L3{A,B} + L3{B,C] + L3{C,E]

[0092] The controller node CTR of [Fig. 1] is configured to schedule and trigger the implementation of a control action on any node(s) of the mesh network MN, including itself. For example, this control action is one of the procedures previously described comprising: - the procedure for analyzing or scanning a frequency band or Wi-Fi Scan, - the procedure for checking the availability of a Wi-Fi or Wi-Fi CAC channel, and - the detection procedure or Wi-Fi Sensing.

[0093] In the following, the node(s) designated to execute the control action in question are designated by executing node(s).

[0094] Such a control action is likely to cause more or less severe disruptions to the flows of data packets exchanged on the connections established by the executing node with other nodes of the mesh network, with negative consequences on the quality of service perceived by the users of the wireless communications networks of the node and of the other impacted nodes.

[0095] In the following, devices and methods are presented for controlling and modifying a configuration of connections established by the executing node with other nodes of this wireless mesh network MN, before the implementation by this executing node of an action of controlling a frequency band likely to generate disturbances on the flows of data packets exchanged by the node on the links of the connections established by this node using this frequency band. These devices and methods make it possible to anticipate the disturbance(s) by adapting upstream the configurations of the connections concerned.

[0096] According to one or more embodiments, the controller node CTR comprises a device 100 for managing a plurality of nodes of a wireless network, such as that of [Fig.l], the nodes of which are access points to wireless communication networks. Such a device is configured to:

[0097] - obtain information relating to the control action to be executed on one of said frequency bands by the at least one executing node,

[0098] - trigger the transmission by the controller node, to at least one node, said impacted node, of the plurality of nodes, comprising said at least one executing node, said impacted node having established at least one multi-link connection with at least one other node of said plurality of nodes, said at least one connection comprising at least two links using distinct frequency bands among which one link, called the impacted link, uses said frequency band on which the control action must be executed, of a request for modification of the configuration of said at least one multi-link connection, for the impacted link, said modification of configuration being a function of said control action, and,

[0099] - upon receipt by the controller node, from said at least one node impacted, of a confirmation of modification of configuration of said at least one connection, transmit to said controller node information indicating that said control action on said frequency band is ready to be executed.

[0100] Thus, according to one or more embodiments, the device 100 implements a method for managing a plurality of nodes of a wireless network which will be described below in relation to [Fig.4]. The device 100 can be implemented in various ways, software and / or hardware. An example of hardware structure of the device 100 will be described below in relation to [Fig. 13].

[0101] According to one or more embodiments, each node of the mesh network MN comprises a device 200 for processing a request to modify a configuration of a node of a wireless network, said node having established at least one multi-link connection with at least one other node of said network, said device being configured to: - obtaining a request for modification of configuration of at least one connection for the multi-link connection link using a given frequency band, received by said node, from the controller node of said wireless network, said notification comprising a command for deleting an authorization for transmission and reception of data on said link for said at least one connection, for at least one type of data flow, - triggering the transmission by said node to said at least one other node of a first request for renegotiation of said connection, implementing said command for deleting an authorization for transmission and reception of data on said link for said at least one connection, for the at least one type of data flow, and - following the renegotiation of said connection, trigger the transmission by said node of a message comprising a report of execution of the configuration modification to the controller node.

[0102] Thus, according to one or more embodiments, the device 200 implements a method for processing a modification of a configuration of a connection which will be described below in relation to [Fig. 5]. The device 200 can be implemented in various ways, software and / or hardware. An example of hardware structure of the device 200 will be described below in relation to [Fig. 13].

[0103] We now present in relation to [Fig. 3], a method for managing a plurality of nodes of a wireless communication network. In the following, we consider that the method is implemented by a device integrated into a controller node, which can be any one of the nodes of the mesh network. The controller node is distinguished from the other nodes in that it is equipped with the functionalities of a controller as specified for example by the EasyMesh standard, while the other nodes are equipped by the same standard with functionalities for executing the commands of the controller node. In both cases, these functionalities can be for example implemented in the node in the form of a computer program, called an agent.

[0104] In the following, we consider for example the controller node CTR of [Fig.l], which corresponds to the access equipment A.

[0105] During a step 30, the device 100 of the controller node CTR obtains ICA information relating to a control action CA programmed by the controller node to be executed on a given frequency band by at least one node of the mesh network MN, called the executing node. This ICA information comprises at least one identifier of the control action CA and an identifier of the node(s) which must execute it. Optionally, it may also comprise additional information elements relating for example to a type of disturbance caused by the execution of this control action on the connection(s) established by the node with other nodes of the mesh network.

[0106] During a step 31, the device 100 obtains information T_M0D relating to a type of configuration modification, at least as a function of the information ICA relating to the control action.

[0107] Depending on the CA control action to be executed, the type of configuration modification includes an interruption of data traffic on said impacted link or a reduction of data traffic on said impacted link, said removal of an authorization to transmit and receive data on said link does not concern all types of data flows.

[0108] According to one or more embodiments, the T_M0D information relating to a modification type is included in the ICA information as an element additional information. Alternatively, it is obtained from all or part of the ICA information, for example the identifier of the control action CA which is then used as a search index to access the additional information elements which are stored in a memory, for example of the device 100 or of the controller node CTR.

[0109] Depending on the CA control action programmed to be executed, other nodes than the executing node(s) may be impacted. Optionally, during a step 33, the device 100 obtains, at least from the ICA information obtained, a list L_IMP of the nodes of the mesh network that will be impacted by the execution of the CA control action at the executing node. This list includes at least the executing node.

[0110] According to one or more embodiments, this list L_IMP is obtained from information relating to a radio signal level RSSI received by the plurality of nodes of the mesh network from the other nodes and a given minimum level threshold TH. This RSSI information is obtained at 32 by the device 100. For example, it reads it from a memory where it has been previously stored, or it receives it from some of the nodes of the wireless network MN on request.

[0111] This second option makes it possible to take into account the current state of the MN network and is illustrated by [Fig.4]. The device 100 triggers the sending by the controller node CTR, at 321, of a neighborhood report request to certain nodes of the plurality of nodes of the mesh network MN.

[0112] This neighbor report request instructs the node that receives it to listen to a given frequency band, typically the one concerned by the programmed control action, and to determine, for each detected radio signal, information relating to a received radio signal level RSSI (Received Signal Strength Indication). For example, the node implements a neighbor report procedure as specified by the IEEE 802.1 lk-2008 standard, which allows a Wi-Fi access point (AP) to collect information on neighboring access points and which operates as follows: - The node sends a Neighbor request to other neighboring APs to obtain information about their networks and capabilities, - Neighboring nodes respond to the request in a Neighbor response including information about their identity and capacity, including the different frequency bands they are capable of using, - The node listens to the given frequency band and determines for each radio signal received from another access point, typically a beacon frame, RSSI information, - The node compiles the received information into a structured neighborhood report. This report is then transmitted to the requesting node, in this case the controller node, for example using a message conforming to the EasyMesh protocol.

[0113] The device 100 obtains the neighborhood reports received by the controller node of the concerned nodes of the MN network at 322.

[0114] The device 100 is configured to use the RSSI information received from a node of the plurality of access point nodes to determine a range measurement of each of them. To do this, at 323 it selects a current node NC and for each of the RSSI information contained in its neighborhood report, it uses at 324 a given threshold TH, for example set at -75 dBm and compares the value of this RSSI information of radio signal level received from a neighboring node NV by the current node NC to the threshold TH. If the signal level information received from the neighboring node NV is greater than the given threshold TH, it considers that a transmission from the neighboring node occupies the radio medium of the current node and therefore that the current node is within range of the neighboring node. In other words, if the neighboring node NV executes a control action on the frequency band, the current node NC will potentially be impacted.

[0115] The device 100 then adds the current node NV to an impact list L_IMP(NV) of the neighboring node. Otherwise, when the RSSI information is less than or equal to the threshold TH, it considers that the neighboring node is not “visible” to the current node and moves on to the RSSI information received from another neighboring node by the current node. It repeats the operation for all the RSSI information of the neighborhood report of the current node.

[0116] Once the neighborhood report of the current node is processed, it moves on to a next node and repeats the operations previously described, until the plurality of nodes are processed.

[0117] This analysis allows it to construct an impact list for each node of the plurality of nodes. At 326, it combines the impact lists associated with the executing node(s) and obtains the list L_IMP(CA) of the nodes impacted by the programmed CA control action.

[0118] During a step 34, the device 100 transmits to the impacted node(s) of the list L_IMP a message comprising a first notification or request RQ1_RCFG for modification of the configuration of its connection(s) with other nodes comprising a link which uses the given frequency band, called the impacted link.

[0119] This message can be sent on one or more links of the multi-link connection(s). An advantage of sending it on all links is to increase the chances that it will be received by the destination node.

[0120] The requested configuration modification depends on the control action and in particular on the type of disturbance that it is likely to cause. According to one or more embodiments, the configuration modification request is constructed from the modification type T_M0D obtained at 31.

[0121] In particular, when the type of configuration modification T_M0D comprises a reduction of the connection on the impacted link, the request for modification of the configuration of said at least one connection comprises a notification of deletion of an authorization for transmission and reception of data on said impacted link for at least one type of data flow.

[0122] On the other hand, when the type of configuration modification T_MOD comprises an interruption of the connection on the impacted link, the request for modification of the configuration of said at least one connection comprises a notification of deletion of an authorization for transmission and reception of data on said impacted link for all types of data flows.

[0123] For example, for a CA control action of the scanning type of a given frequency band (Wi-Fi scan) or of the verification type of availability of a given frequency band (Wi-Fi CAC), the configuration modification consists of completely interrupting the traffic on the impacted link. On the other hand, for a control action of the variation analysis type upon reception of data on a given frequency band (Wi-Fi sensing), the data traffic can only be reduced, by eliminating the use of the impacted link for certain types of data flows.

[0124] For example, the type of flow concerned by this deletion is a type of flow associated with strong latency constraints, for example a real-time flow of the video or voice type.

[0125] During a step 35, the device 100 receives from the impacted node(s) an RP1_RCFG message acknowledging the modification of the requested configuration, comprising for example an execution report.

[0126] During a step 36, the device 100 informs the controller node, for example by sending it a STRT-CA message, that the required configuration modifications have been made and that it can trigger the execution of the CA control action on said frequency band.

[0127] During a step 37, it obtains from the control node CTR an END_CA information item indicating the end of execution of the control action by the executing node(s), for example it obtains a message comprising for example a report of execution of the control action CA received from the controller node from the executing node.

[0128] At 38, the device 100 triggers the transmission by the controller node of a message comprising a second configuration modification request or notification. RQ2_RCFG to the affected nodes. It includes a request to restore the configuration of the at least one connection. Similarly, this message can be sent on one or more links of the multi-link connection(s). An advantage of sending it on all links is that it increases the chances of it being received by the destination node.

[0129] During a step 39, the device 100 obtains a second RP2_RCFG message acknowledging the modification of the configuration, received from the controller node from the impacted node(s) and comprising for example a report of execution of the requested configuration restoration.

[0130] The method which has just been described allows a controller node to synchronize a renegotiation by the node(s) of the multi-link connections which will be impacted by the execution of the CA control action. To do this, according to one or more embodiments, the device 100 relies on messages whose format is specified by the EasyMesh standard.

[0131] According to one or more embodiments, the configuration change notification message RQ1_RCFG may be a single message sent to all the impacted nodes and to which each of the impacted nodes will respond with a configuration change acknowledgment message RP1_RCFG.

[0132] This is for example an IEEE 1905 type reconfiguration transaction comprising a request message including information relating to a list of multi-link connections to be reconfigured and a response message sent following the application by each of the impacted nodes of the configuration. Such a transaction is described in the EasyMesh R6 specification, section 7.4 of the draft 6th revision of the EasyMesh Wi-Fi_EasyMesh_Specification_DRAFT_R6-240208b specification. For example, this EasyMesh reconfiguration transaction is constructed as follows: - A request of type “AP MLD Configuration Request message” (specified in the EasyMesh R6 Specification, Section 17.1.63), and - A Response of type “AP MLD Configuration Response message” (specified in the EasyMesh R6 Specification, Section 17.1.64).

[0133] The "AP MLD Configuration Request message" includes a TLV information field titled "Agent AP MLD Configuration TLV" (specified in the EasyMesh R6 Specification, Section 17.2.96). More generally, a TLV information field contains information of the type "Type, Length, Value", where "Type" designates a type of information or parameter included in the field, "Length" indicates the length of the field, specified in bytes or bits, and "Value" contains the actual data associated with the specified type. An advantage of a TLV information field is that it allows the addition of new types information without requiring major changes in the underlying standard or protocol.

[0134] More specifically, the TLV field “Agent AP MLD Configuration TLV” describes connection configuration parameters, in particular the links authorized to transport data packet streams. These parameters will be detailed below.

[0135] More specifically and in relation to [Fig.4], the TLV information field “Agent AP MLD Configuration” includes the following elements:

[0136] - a list of multi-link connections or Multi-Link Description MLD (for “Multi- Link Description”, in English), the number of which is given by the “Value” field titled 'Number of MLD'.

[0137] -For each multi-link connection, the MLD element includes the following information fields:

[0138] - a Wi-Fi network identifier SSID,

[0139] - a MAC address dedicated to this multi-link connection,

[0140] - a list of access equipments whose number is given by the field 'Num Affiliated APs'. For each access device in this list, the information field "Agent AP MLD Configuration" includes a description according to the EasyMesh standard of this access device, including a MAC address of the access device "AP MAC Address", a unique radio identifier RUID ("Radio Unique Identifier"), a "link-ID" identifier of the link in the multi-link connection

[0141] The device 100 sends this message to notify the nodes of the mesh network identified as impacted by the CA control action, of the new configuration to be adopted. This message indicates the multi-link connections concerned and their composition.

[0142] Once the configuration change has been made, each impacted node responds to the controller node using a response message. This message has two functions, the first to acknowledge the configuration change and the second to update the multi-link connection configuration information at the controller node.

[0143] The response message “AP MLD Configuration Response message” includes the TLV information field “Agent AP MLD Configuration TLV” detailed above, in which for each multi-link connection, the node concerned has completed the AP MAC Address, RUID and Link_ID information fields, and another TLV type information field called “EHT Operations TLV” (specified in the EasyMesh R6 specification, Section 17.2.103), the content of which corresponds to that of the Wi-Fi7 configuration and will be detailed below in relation to [Fig.6].

[0144] In relation to [Fig.5], a method is now described for processing a request to modify a configuration of a multi-link connection established by a node of a wireless network, according to one or more embodiments. In the following, it is assumed that the method in question is implemented by a device 200 as described previously, in relation to [Fig.l]. Such a device 200 is embedded in a node of the wireless network, for example an access device of the mesh network MN of [Fig.l], forming part of the nodes identified as likely to be impacted by the control action programmed to be executed by said at least one node executing on a given frequency band. This impacted node can therefore be the node or one of the executing nodes or another node, depending on the programmed control action.

[0145] In the following, it is assumed that this impacted node has established at least one multi-link connection with at least one other node of the wireless network.

[0146] During a step 51, the device 200 obtains a request message RQ1_RCFG for modifying the configuration of at least one multi-link connection established by said impacted node received by said node from the controller node CTR of said wireless mesh network. This message can be received on one or more links of the multi-link connection(s).

[0147] According to one or more embodiments, this request comprises a command to remove an authorization to transmit and receive data on the link of said connection using the frequency band concerned by the link control action for said at least one connection, for at least one type of data flow,

[0148] At 52, the device 200 sends to said other node a message comprising a first request RQ1-CNX to renegotiate said connection, comprising configuration instructions implementing the command to remove an authorization to transmit and receive data on said link for said at least one connection, for said at least one type of flow.

[0149] According to one or more embodiments, these configuration instructions specify, for said at least one connection, the links authorized for the transmission and reception of data streams and they therefore do not include said link for said at least one data stream.

[0150] For example, the configuration instructions are specified using an information field called "Traffic ID to Link Mapping" to specify the links to be used for the multi-link connection. For example, the TID-To-Link Mapping field indicates an ordered binary sequence (in English "bitmap") according to which each bit corresponds to a link of the multi-link connection, the corresponding link being allowed when the bit is 1 and prohibited when it is 0.

[0151] Following the renegotiation of said connection, the device 200 transmits at 53, from the impacted node, a response message RP1-CNX comprising a configuration change execution report to the controller node.

[0152] At 54, the device 200 obtains a configuration restoration request message received by the impacted node from the controller node, comprising a command to add an authorization for transmission and reception of data on said link for said at least one connection, for said at least one type of flow.

[0153] At 55, the device 200 triggers the transmission by the impacted node and to the other node to which it is connected via said connection, of a message comprising a second request RQ2_CNX for renegotiation of said at least one connection, comprising configuration instructions, implementing the command for adding an authorization for transmission and reception of data on said link for said at least one connection, for said at least one type of flow.

[0154] According to one or more embodiments, these configuration instructions specify for said at least one connection the links authorized for the transmission and reception of data flows and they include said link for said at least one type of flow.

[0155] At 56, the device 200 triggers the transmission by the impacted node and to the controller node, of an RP2_RCFG message comprising a report of execution of the reestablishment of the configuration of said at least one connection.

[0156] According to one or more embodiments, when said impacted node has established several connections implementing a link using the given frequency band, the successive messages RQ1_CNX of first connection renegotiation request and the message RQ2_CNX of second connection renegotiation request are sent to said plurality of other nodes connected to it via these connections.

[0157] In this way, each of the impacted nodes renegotiates a first time the multi-link connections that it has established with other nodes to adapt their configurations at the request of the controller node, before the execution of the programmed control action on the given frequency band, then a second time, once the control action is finished, at the request of the controller, to reestablish the initial configurations.

[0158] According to one or more embodiments, the connection renegotiation request messages comply with the Wi-Fi7 standard, in particular section IEEE802.11be Draft 4.0 §35.3.7 Link management.

[0159] According to this section, when negotiating a multi-link connection with a station equipment that wishes to attach to it, an access equipment can define information relating to one or more types of flows authorized on each of the links of this connection. This information is described in a management frame (in English, "beacon") that it periodically emits in its local LAN to announce its capabilities, particularly in terms of QoS, and that stations and other access points listen to. The information obtained allows a station to determine which Wi-Fi networks are available and decide to which access point they will connect. The management frame includes other essential information about the local network, such as the name of the SSID (Service Set Identifier) ​​network, security capabilities, supported channels, timeouts, etc. For another access point, they allow it to know the neighboring access points visible through the radio medium and therefore to coordinate using the EasyMesh protocol.

[0160] This information relating to the types of flows authorized on a given link is also described in another management frame, called a probe response sent by an access equipment (AP) in response to a probe request issued by a station wishing to connect to the access equipment. The probe response includes other essential information on the local network of the access equipment, such as its SSID name, its security capabilities, etc., to allow the requesting station to decide whether it wishes to associate itself with this "access equipment".

[0161] This information is also exchanged when a station is associated with the access equipment. It can finally be sent by the access equipment to the stations connected to it to renegotiate the connection, by modifying the types of flows authorized on the link.

[0162] In all cases, an information element called Traffic Identifier to Link (TID-To-Link Mapping), describes the association of a traffic identifier (TID), which identifies a specific data flow or traffic type, with a link of the multi-link connection.

[0163] In this regard, a traffic identifier (Traffic Identifier) ​​refers to any identifier usable by upper layer entities to distinguish the medium access control (MAC) service data units (MSDUs) of the MAC entities that support quality of service (QoS) within the MAC data service.

[0164] There are 16 possible values ​​for the traffic identifier, including 8 that identify TC traffic categories (for "Traffic Categories") distinguishing between voice, video, best effort and background traffic, each of which has specific quality of service (QoS) requirements in terms of delay, jitter, packet loss, etc.

[0165] The other 8 possible values ​​identify parameterized traffic streams (TS) i.e. specific data flow types in a Wi-Fi network that are associated with parameters of specific transmission. These data flows are characterized by parameters such as bit rate, transmission delays, bandwidth requirements, etc., which are used to provide Quality of Service (QoS) guarantees for delay-sensitive applications such as Voice over IP (VoIP) or video streaming. They can be combined with QoS management mechanisms such as WMM (Wi-Fi Multimedia) within the framework of the IEEE 802.11 standard.

[0166] The traffic identifier TID is assigned to a service data unit MSDU in the layers of the OSI model that are higher than the MAC layer. This ensures a correspondence between the IP layer (TOS / DSCP field) and the Wi-Fi MAC layer (TID) in order to manage the transmission. Once the packet is categorized, the information is integrated into the Wi-Fi header. This allows the Wi-Fi protocol to treat a flow category independently once this flow is identified and marked with the TID associated with the traffic type.

[0167] More specifically, according to the IEEE802.1 Ibe 9.4.2.314 TID amendment, the Traffic Identifier to a Link (TID-To-Link Mapping) takes the form of a TLV type information element, whose "Value" information field indicates, for each link of the multi-link connection, the types of traffic that can pass through this link. If no traffic type is defined for a link, it is considered that this link is no longer usable. By default, all types of traffic are authorized on all links.

[0168] According to one or more embodiments, this TID-To-Link Mapping information element is used in the connection renegotiation request messages RQ1_CNX and RQ2_CNX addressed by the nodes of the mesh network impacted by the programmed CA control action, to respond to the requests for modification of the configuration of their connections received from the controller node.

[0169] In relation to Figures 6 and 7, an example of implementation of the renegotiation mechanism of a multi-link connection is now detailed, according to one or more embodiments. In particular, the case of a total interruption of transmissions and reception on the link using the frequency band concerned by the programmed control action is considered.

[0170] For example, the device 200 is configured to transmit this TID-To-Link Mapping field in an action frame, as defined for example in the IEEE 802.1 Ibe Draft 4.0 amendment, an "Action Frame". According to one embodiment, this is a particular type of control frame used by a node of a Wi-Fi wireless network to trigger a specific action from another node.

[0171] For example, in relation to [Fig.6], the action frame used is a recommendation concerning link parameters for communications in a Wi-Fi network operating in “Extended High Speed” EHT mode (from the English, "Extended High Throughput"). The connection renegotiation message RQ1_CNX then takes the following form:

[0172] IEE 802.11 Action No Ack, Flags:.......C

[0173] IEE 802.11 Wireless Management

[0174] Fixed parameters

[0175] Category code: Protected EHT (37) Protected EHT Action: EHT Link Recommendation (7)

[0176] Reason code: Unspecified Reason (0x0001)

[0177] Ext Tag: AID Bitmap (702.1 Ibe D3.0)

[0178] Ext Tag length: 3 (Tag len 4)

[0179] Ext Tag Nurnber: AID Bitmap (802.1 Ibe D3.0) (134)

[0180] Partial AID Bitmap Eength: 1

[0181] Bitmap Control: 0x44

[0182] .......0 = Reserved 0x0

[0183] 0100 010. = Bitmap offset 0x22

[0184] Partial AID Bitmap: 01

[0185] Association ID : 0x0220

[0186] Ext Tag : Multi-Link Traffic Indication (802.11be D3.0)

[0187] Ext Tag length : 3(Tag len: 4)

[0188] Ext Tag Nurnber: Multi-Link Traffic Indication (802.11be D3.0 (110)

[0189] Multi-Link Traffic Control : 0x2202, Bitmap Size: 3

[0190] ............0010 = Bitmap Size: 3

[0191] .010 0010 0000 .... = AID Offset: 544

[0192] 0...............= Reserved : 0x0 Traffic Indication List: 05

[0193] Taggedparameters ( 18 bytes)

[0194] Renégociation rajout du lien L2 :

[0195] La ligne « Protected EHT Action : EHT Link Recommendation (7) » indique que le message est de type « recommandation des liens ».

[0196] The line "Traffic Indication List: 07" describes the composition of the links using a bit mask of the authorized links. In binary, 0x5 is 101, which corresponds to Ll=l, L2=0, L3=l. The L2 link is therefore not authorized for the connection.

[0197] Once the control action is completed, each impacted node transmits, upon receipt of a configuration reestablishment request RQ2_RCFG from the controller node, a second renegotiation request RQ2_CNX with the other node(s) with which it has established a multi-link connection to reauthorize the temporarily prohibited link.

[0198] According to the example of [Fig.6], the configuration restoration instructions are transmitted in a link recommendation type action frame in EHT Extended Broadband mode and the “Traffic Indication List” parameter is this time set to 0x7. In binary, this value corresponds to the binary sequence 111, which indicates Ll=l, L2=l, L3=l. Once this configuration modification is implemented, all the links of the multi-link connection between nodes A and B are authorized again.

[0199] In relation to [Fig.7], an example of implementation of the methods which have just been presented is now described in the case where the programmed control action is a Wi-Fi Scan procedure for analyzing or scanning a given frequency band among the available frequency bands. With reference to [Fig.l], it is assumed that the controller node CTR has programmed the execution of this Wi-Fi Scan control action on one of the 5GHz frequency bands, for example the low band 5150 MHz - 5350 MHz. In the example of [Fig.l], the controller node CTR and the node A are one and the same access equipment. Nevertheless, the description which follows applies equally well when the two nodes are separate access equipment.

[0200] The impact of a Wi-Fi Scan control action on the CAB multi-link connection established by the executing node A is defined as a transmission and reception cutoff on the link using the given frequency band for the entire duration of the scan which is approximately 20 seconds.

[0201] Only the executing node will be prevented from transmitting and receiving on this link. It is therefore the only node in the mesh network impacted by the execution of this control action.

[0202] In this example, considering node A, the Wi-Fi Scan control action will have an impact on the L2{A,B] link of the CAB connection which uses the 5GHz frequency band.

[0203] For this Wi-Fi Scan control action, the proposed solution is therefore to renegotiate the multi-link connection to remove the L2 link from the CAB connection.

[0204] In relation to [Fig.7], the device 100 of the controller node CTR obtains at 30 the ICA information relating to the programming of an ICA control action of the Wi-Fi Scan type on the node A of the wireless network MN that it controls. It notifies the node A by sending it at 34 a request RQ1_RCFG for modification of the configuration of its CAB connection. It indicates that the authorization to transmit and receive on the L2 link must be removed. The device 200 of the node A receives this request and triggers a renegotiation of its CAB connection with the node B by sending it at 52 a request for renegotiation of the connection RQ1_CNX in which the transmission and reception of data on the L2 link are not (any longer) authorized regardless of the type of data traffic.

[0205] For example, node B chooses, according to proprietary decision logic, to use the authorized L3 link instead of the deleted L2 link.

[0206] Upon receipt of a response message RP1_CNX from node B, the device 200 of node A confirms at 53 to the controller node CTR that the connection has been renegotiated (RP1_RCFG). Upon receipt, the device 100 of the controller notifies (STRT WI-FI SCAN) at 36 the controller node that it can trigger the Wi-Fi Scan control action.

[0207] With reference to [Fig.8], following this first renegotiation of the multi- CAB links, the impact on the previously defined data packet flows is as follows: - Between A and C: AC (fl): L1{A,B} + L{B,C]

[0208] AC (f2): L3{A, B] + L2{B, C]

[0209] AC (f3): L3{A, B] + L3{B, C] - Between A and D: AD (fl): L1{A,B]+L1{B,D]

[0210] AD (f2): L3{A, B] + L2{B, D]

[0211] AD (f3): L3{A, B] + L3{B, D] - Between A and E: AE (fl): L1{A, B] + L1{B, C] + L1{C, E]

[0212] AE (f2): L3{A,B] + L2{B,C] + L2{C, E]

[0213] AE (f3) : L3{A, B] + L3{B, C] + L3{C, E]

[0214] The controller node CTR triggers the Wi-Fi Scan action by sending an RQ_CA command to node A, which performs the Wi-Fi Scan for 20 seconds and then transmits an RP_CA execution report of the Wi-Fi Scan to the controller node. As soon as it is informed (END Wi-Fi SCAN), the device 100 of the controller node CTR notifies node A by sending it at 38 an RQ2_RCFG request to reestablish the configuration of its CAB connection. It indicates that the authorization to transmit and receive on the L2 link, previously deleted, must be added. The device 200 of node A receives this request at 54 and triggers a renegotiation of its CAB connection with node B by sending it at 55 a RQ2_CNX connection renegotiation request in which the transmission and reception of data on the L2 link is again authorized regardless of the type of data traffic.Upon receipt at 56 of a confirmation from node B, the device 200 of node A confirms at 57 to the controller node the restoration of the initial configuration for the CAB connection.

[0215] In relation to Figures 9-11, an example of implementation of the methods which have just been described is now described in the case where the programmed control action is a Wi-Fi Sensing procedure for detection upon reception of packets. of data on a given frequency band among the available frequency bands. With reference to [Fig.l], it is assumed that the controller node CTR has programmed the execution of this Wi-Fi Sensing control action on the 5GHz frequency band between nodes A and B, which are considered in the following as both executors, even if in it is A that is designated to initiate the Wi-Fi Sensing procedure and B only reacts. In the example of [Fig.l], the controller node CTR and node A are a single access device. However, the following description applies equally well when the three nodes CTR, A and B are separate access devices.

[0216] The action is based on an exchange of packets at short intervals between node A and node B. The duration of the disturbance is estimated at 10 seconds. The impact of a Wi-Fi Sensing control action can be defined as a significant reduction in the transmission and reception on the L2 links using the 5GHz frequency band of all connections established by both nodes A and B during the duration of the exchange of data packets.

[0217] The impact study for this Wi-Fi Sensing action is therefore potentially more complex than that of the Wi-Fi Scan action. More precisely, since nodes A and B will each transmit and receive data packets on the 5GHz frequency band to execute the Wi-Fi Sensing action, the impact zone can be defined as all the nodes of the mesh network that use this 5GHz frequency band and that are close enough to nodes A and B to be affected by this exchange of packets, i.e. to detect the resulting radio signals. For example, the proximity of a node to another node can be deduced from information on the received radio signal level RSSI (from the English, "Received Signal Strength Indication"), provided by the node in question to the other node, and the comparison with a given threshold TH, for example set at -75dBm, as previously described in relation to [Fig.4].In this case, the nodes of the MB mesh network which have indicated a received signal level information RSSi higher than the given threshold TH are considered to be impacted by the programmed Wi-Fi Sensing control action.

[0218] According to one or more embodiments, this impact study is implemented by the device 100 of the CTR controller node.

[0219] The latter can retrieve and group the information concerning the signal level RSSI received by each node from each other node of the mesh network MN, for example by triggering at each node of the plurality of nodes of the mesh network, the implementation of a neighbor report procedure as specified in the IEEE 802.11k standard.

[0220] As an illustrative and non-limiting example, we can consider setting a minimum radio signal level threshold TH at -75dBm. Thus, for a given node, all its neighbors "visible" at more than TH = -75dBm, i.e. whose node receives radio signals with a radio signal level higher than the TH threshold, are considered to impact it. In other examples, the given threshold TH is chosen from a range of values, for example, between -70dBm and -80dBm. This value can be configured according to the topology of the wireless network MN (for example, its number of nodes), its environment (indoors, outdoors, in the presence of neighboring wireless networks), or the reception sensitivity of the constituent nodes of said wireless network MN.

[0221] Thus, it is possible to determine from the neighborhood reports and the threshold TH, for each node of the mesh network, whether it is within range of an executing node; then to establish a list of nodes which will be impacted by the transmissions of the executing node, and to deduce therefrom a list L_IMP of the nodes impacted by the Wi-Fi Sensing action by joining the lists of nodes impacted by the transmission of each executing node, here A and B. As previously described, this list of impacted nodes L_IMP is then used by the device 100 to modify the configurations of all the connections impacted by the programmed Wi-Fi Sensing control action.

[0222] In relation to [Fig.9], a measured impact zone ZIA-ZID is presented for each node of the mesh network MN. This is measurable for each node, from the received radio signal level information RSSI, which makes it possible to determine whether the node in question is within range or not of the transmission of another node.

[0223] In the example considered, it is thus possible to deduce that: - a transmission from node A: impacts node B, - a transmission from node B: impacts nodes A, C and D, - a transmission from node C: impacts nodes B and E, - a transmission from node D: impacts node B, - a transmission from node E: impacts node C.

[0224] A bi-directional measurement transmission by the Wi-Fi Sensing procedure between nodes A and B will therefore impact the union of their respective lists, i.e. L_IMP = {B, A, CetD}.

[0225] This implies that all L2 links established between nodes of the MN mesh network and comprising one of these four nodes will be impacted by the Wi-Fi Sensing procedure.

[0226] Therefore, according to one or more embodiments, the device 100 is configured to request each of the nodes in the L-IMP list to modify its configuration in order to execute the Wi-Fi Sensing control action programmed at nodes A and B.

[0227] In relation to [Fig. 10], we now describe the message flows between the controller node CTR and the nodes of the wireless network MN which are impacted by an action of network control, of the Wi-Fi Sensing type, programmed, according to one or more embodiments. It is assumed here that the device 100 has already carried out the impact study and that it has the list L_IMP of the impacted nodes, for example stored in a memory of the device 100 or of the controller node CTR.

[0228] The device 100 is configured to transmit (step 34) a first configuration modification request RQ1-RCFG to the nodes of the list L_IMP, in this case A, B, C and D to ask them to remove the L2 link (which uses the 5GHz frequency band) from their connections established with other nodes of the mesh network MN. For example, it transmits a single message which is intended for all the nodes concerned. Alternatively, it transmits a message to each of the nodes concerned.

[0229] Upon receipt, the device 200 of node A renegotiates the links to be used with node B in order to no longer use the link L2{A,B] and to use the links L1{A,B] and L3{A,B] instead. To do this, it applies proprietary logic which may in particular take into account the capacities of the other available links and load balancing constraints on these different links. In practice, each radio uses a different frequency band from the other radios, and the 2.4GHz frequency band (L1) has a significantly lower capacity than the 5GHz frequency band (L2) and even more so than the 6GHz frequency band (L3). In this case, the device 200 of node A decides to replace L2 with L3 which has the highest bandwidth.

[0230] According to one or more embodiments, the device 200 of the node A transmits (step 52) to the node APB a connection renegotiation request RQ1_CNX in which it indicates that the links to be used are L1{A,B] and L3{A,B}. In other words, it has deleted the link L2 {A,B} from the list of authorized links.

[0231] Similarly, the device 200 of the node B renegotiates the links to be used with the node C in order to no longer use the link L2{B,C] and to use the links L1{B,C] and L3{B,C] instead. To do this, according to one or more embodiments, the device 200 of the node B transmits (step 52) to the node C a connection renegotiation request RQ1_CNX in which it indicates that the links to be used are L1{B,C] and L3{B,C}. In response, it receives an acknowledgment message RP1_CNX (not shown) from the APC node (step 53).

[0232] The device 200 of node B also renegotiates, in a similar manner, the links to be used with node D in order to no longer use the link L2{B,D] and to use the links L1{B,D] and L3{B,D] instead. In response, it receives an RP1_CNX acknowledgment message (not shown) from node D (step 53).

[0233] Similarly, the device 200 of the node C renegotiates, in a similar manner, the links to be used with the node E in order to no longer use the link L2{C,E] and to use the links L1{C,E} and L3{C,E} instead. In response, it receives an RP1_CNX acknowledgment message (not shown) from the APE node (step 53).

[0234] As for device 200 of node D, it does not renegotiate any connection, because its link with node B has already been processed by node B.

[0235] Then, each of the nodes A, B, C and D acknowledges (step 54) the configuration modification made in response to the RQ1-RCFG request to interrupt their respective L2 link, for example by sending an RP1_RCFG acknowledgment message to the controller node CTR.

[0236] At this stage, the renegotiated connections are configured as illustrated in [Fig.11]: - Between A and C: AC(fl): L1{A,B}+L2{B,C]

[0237] AC(f2): L3{A,B} + L3{B,C]

[0238] AC (f3): L3{A,B] + L3{B, C] - Between A and D: AD (fl): L1{A,B]+L1{B,D]

[0239] AD (f2): L1{A, B] + L1{B, D]

[0240] AAD (f3): L3{A, B] + L3{B, D] - Between A and E: AE (fl): L1{A,B] + L1{B,C] + L1{C,E]

[0241] AE (f2): L3{A,B] + L3{B,C] + L3{C,E]

[0242] Once it has received (step 35) confirmation from each node in the L_IMP list that the configuration modification request RQ1_RCFG has been taken into account, the controller node triggers the execution of the Wi-Fi Sensing programmed control action by sending an execution request RQ1_CA to node A.

[0243] Wi-Fi Sensing takes place between nodes A and B for 10 seconds following the controller's request.

[0244] Once Wi-Fi Sensing is performed, node A returns an RP_CA acknowledgment message including a report of execution of the Wi-Fi Sensing control action to the controller node CTR.

[0245] Upon receipt of an end of execution notification (step 37), the device 200 of the controller node transmits (step 38) to the impacted nodes a second configuration modification request RQ2_RCFG to ask them to reestablish the L2 link in their respective connections. To do this, it indicates for example that the L2 link is authorized. For example, it transmits a single message which is intended for all the nodes concerned. Alternatively, it transmits a message to each of the nodes concerned.

[0246] Upon receipt, node A renegotiates the links to be used with node B in order to use the link L2{A,B] again. To do this, according to one or more embodiments, the device 200 of node A transmits (step 56) to node B a connection renegotiation message RQ2_CNX in which it indicates that the links to be used are L1{A,B], L2{A,B] and L3{A,C}. In response, it receives an acknowledgment message RP2_CNX (not shown) from node B (step 57).

[0247] Similarly, node B renegotiates the links to be used with C in order to use link L2{B,C] again.

[0248] Node B also renegotiates the links to be used with D in order to use link L2{B,D] again.

[0249] Node C renegotiates the links to be used with E in order to use link L2{C,E] again.

[0250] Node D has no links to renegotiate.

[0251] Then, once their connections are reestablished, nodes A, B, C and D acknowledge the restart of the L2 link to the controller (step 58), for example by sending an RP2_RCFG message.

[0252] In relation to Figs 12A-12C, an example of a method for modifying a configuration of the connections established by the nodes of a wireless network according to another embodiment is now described. In this example, the solution based on the renegotiation of the use of multi-links makes it possible to indicate which types of traffic, in other words specific data flows, are authorized to use each of the links of the connection.

[0253] For example, the traffic types considered include background type BK (from the English, "background"), best effort type BE (from the English, "best effort"), video type VI (from the English, "video") and voice type VO (from the English, "voice"). These different traffic types are each associated with specific requirements in terms of transmission conditions. For example, data flows of type VI or VO are associated with real-time transmission conditions (in English, "live") and therefore with high latency and packet loss constraints.

[0254] According to the Wi-Fi standard and as indicated in the table of [Fig. 12A], these different types of flows are associated with distinct traffic identifiers (from the English, “traffic ID”). For example, type BE is associated with the identifier value 0, type BK with the value 1, type BE with the value 3, type VI with the value 5 and type VO with the value 6.

[0255] In the following, we note as follows a link of the connection established between A and B on the 2.4GHz frequency band authorizing all types of traffic BK, BE, VI and VO: L1{A,B][BK, BE, VI, VO]. If we remove the data flow of type VI for this link, the notation becomes as follows: L1{A,B](1)[BK, BE, VO].

[0256] In relation to [Fig.l2B], it is assumed, in a nominal state NMN, that all frequency bands are usable (here 2.4GHZ, 5GHz and 6GHz) and that all links of a multi-link connection can accommodate all types of traffic. In other words, the multi-link connections established by the nodes of [Fig.l] are in this nominal state.

[0257] For example, it is assumed that the control action CA programmed on the node PA of [Fig.l] is a Wi-Fi Sensing procedure on the frequency band used by the L2 link and that the impacted nodes are those defined in connection with [Fig.9], namely A, B, C and D. However, during the execution of the Wi-Fi Sensing procedure, the exchange of data packets between A and B in the form of continuous transmission on the given frequency band, for example 5GHz, may disrupt the VI and VO type flows, but the BK and BE type flows are not necessarily strongly impacted. In this case, it is a matter of renegotiating the use of the links to carry out a partial withdrawal of the impacted L2 link excluding the VI and VO flows.

[0258] More generally, it is noted that this embodiment which is now described could be applied to any other control action which has the effect of disrupting the use of the given frequency band, but does not necessarily impose the total interruption of transmissions and receptions of data packets on the links using the given frequency band, in other words when the type of configuration modification T_M0D associated with the programmed control action includes a reduction of the connection on the impacted link.

[0259] According to this embodiment, the request for modification of the configuration of the connection(s) sent to the impacted nodes of the wireless network MN (L_IMP) comprises a notification of removal of an authorization to transmit and receive data on said impacted link for at least one type of data flow, but not for all types of data traffic. For example, it explicitly specifies that the data traffic types VI and VO are not authorized to transit via the link L2. For example, it can also specify that the data traffic types VI and VO must be routed via another link of the connection, for example the link L3, whose frequency band is not the subject of a programmed control action.

[0260] In this way, we distinguish the types of traffic with the most heavily impacted flows (VI, VO) which are temporarily excluded from the L2 link to be temporarily redirected to the L3 link.

[0261] Thus, for a given multi-link connection established by one of the nodes in the L_IMP list, the data flow paths are configured according to their traffic type, as follows: - BK, BE: Same state as the nominal state, i.e. authorized on all links of the multi-link connection, - VI,VO: prohibited on the L2 link and redirected to one of the other links.

[0262] According to the Wi-Fi standard, the information authorizing the use of a type of traffic on a given link of a multi-link connection can be transmitted by the node having established a multi-link connection with another node, to this other node, through an information element of a management frame message or Wi-Fi beacon (in English, "beacon") sent periodically by the node in its local LAN to announce its capabilities, in particular in terms of QoS, but also a configuration to be adopted for the stations which wish to connect to it. For each type of traffic, this information element the authorized links of the connection.

[0263] For example, such an information element indicating the withdrawal of type VI and VO traffic on the L2 link takes the following form:

[0264] Ext Tag: TlD-To-Eink Mapping (802.1 Ibe 03.0)

[0265] Ext Tag length 15 (Tag len: 16)

[0266] Ext Tag Number: TlD-To-Eink Mapping (802.11be3.0) (109)

[0267] TID-To-Link Mapping Control: 0x3a

[0268] Mapping Switch Time: 37607

[0269] Expected Duration: 6000

[0270] Eink Mapping OfTID 0:0x0007 [0271 ] Link Mapping Of TID 1: 0x0007

[0272] Eink Mapping Of TID 2: 0x0007

[0273] Eink Mapping OfTID 3: 0x0007

[0274] Eink Mapping OfTID 4: 0x0005 Link Mapping Of TID 5: 0x0005

[0275] Eink Mapping OfTID 6: 0x0005

[0276] Eink Mapping OfTID 7: 0x0005

[0277] In relation to the table in [Fig. 12A], we understand that the line “Link Mapping Of TID 5: 0x0005” amounts to authorizing type VI flows on links L1 and L3 and prohibiting them on link L2.

[0278] The solution proposed here consists of using, to specify the configuration modification request sent by the controller node to the node(s) impacted by the control action, another TLV type information field than that previously described (TLV AP MLD Configuration Request and Response), for example an information field entitled “TID-to-Link Mapping Policy TLV” as described in the EasyMesh R6 standard, Section 17.2.102.

[0279] This other TlD-To-Link Mapping Policy TLV information field has a similar structure to the previous one, except that it does not indicate a list of access points. Instead, it includes the TID-To-Link Mapping information just described for a Wi-Fi management frame.

[0280] Then, the device 200 of an impacted node is configured to trigger a renegotiation of the multi-link connections that it has established with other nodes, which may be access points or stations, by sending them a connection renegotiation request, which may for example take the form of a generic control message of the action frame type, comprising a TLV TID-to-Link Mapping element as described previously. Indeed, it should be noted that the form of the TLV is the same for a modification request between the controller node and the agent of an impacted node, for example compliant with the EasyMesh protocol and for a multi-link connection renegotiation request, compliant with the Wi-Fi standard between an impacted node and the stations or other access points connected to it.

[0281] In relation to [Fig.l2C], we present the MOD state of the multi-link connection between nodes A and B after the configuration change which has just been described. The data flows VI and VO no longer use the link L2, but are redirected onto the link L3.

[0282] This other embodiment is advantageous insofar as it allows different configurations to be specified depending on the types of data traffic.

[0283] In relation to [Fig. 13], an example of hardware structure of the devices 100 for controlling a configuration of a mesh network according to the invention and 200 for modifying a configuration of a multi-link connection between access equipment of a mesh network according to one or more embodiments of the invention is now described.

[0284] In [Fig. 13], the device 100, 200, comprises at least one processor 110, 210 and at least one memory 120, 220. The device 100, 200 may also comprise one or more communication interfaces. In this example, the device 100, 200 comprises network interfaces 130, 230 (e.g., network interfaces for accessing a wired / wireless network, including an Ethernet interface, a WIFI interface, etc.) connected to the processor 110, 210 and configured to communicate via one or more wired / wireless communication links and user interfaces 140, 240 (e.g., a keyboard, a mouse, a display screen, etc.) connected to the processor. The device 100 may also include one or more media readers 150 for reading a computer-readable storage medium (e.g., a digital storage disc (CD-ROM, DVD, Blue Ray, etc.), a USB flash drive, etc.).The processor 110, 210 is connected to each of the other aforementioned components in order to control their operation.

[0285] The memory 120, 220 may include random access memory (RAM), cache memory, non-volatile memory, backup memory (e.g., programmable or flash memories), read only memory (ROM), a hard disk drive (HDD), a solid state drive (SSD), or any combination thereof. The ROM of the memory 120, 220 may be configured to store, among other things, an operating system of the device 100, 200 and / or one or more computer program codes of one or more software applications. The RAM of the memory 120 may be used by the processor 110, 210 for temporary storage of data.

[0286] The processor 110, 210 may be configured to store, read, load, execute and / or otherwise process instructions stored in a computer-readable storage medium and / or in the memory 120, 220 such that, when the instructions are executed by the processor, the device 100, 200 executes one or more or all of the steps of the method for controlling, respectively modifying, a configuration, described in this document. Means implementing a function or a set of functions may correspond in this document to a software component, a hardware component or a combination of hardware and / or software components, capable of implementing the function or the set of functions, according to what is described below for the means concerned.

[0287] The present description also relates to an information carrier readable by a data processor, and comprising instructions of a program as mentioned above. The information carrier may be any hardware means, entity or apparatus, capable of storing the instructions of a program as mentioned above. Usable program storage media include ROM or RAM memories, magnetic storage media such as magnetic disks and magnetic tapes, hard disks or optically readable digital data storage media, or any combination of these media.

[0288] In some cases, the computer-readable storage medium is not transient. In other cases, the information medium may be a transient medium (e.g., a carrier wave) for the transmission of a signal (electromagnetic, electrical, radio, or optical signal) carrying the program instructions. This signal may be conveyed via a suitable transmission means, wired or wireless: electrical or optical cable, radio or infrared link, or by other means.

[0289] An embodiment also relates to a computer program product comprising a computer-readable storage medium having stored thereon program instructions, the program instructions being configured to cause the host device (e.g. a computer, or the device 100 of the controller node, or the device 200 of an impacted node) to implement all or part of the steps of one or more methods described herein when the program instructions are executed by one or more processors and / or one or more programmable hardware components of a host device, such as for example a controller node, respectively an access equipment node of a mesh network.

[0290] The embodiments which have just been presented are not limited to the particular example of a mesh network which has just been presented and they apply to other types of wireless communication networks whose nodes are each equipment for accessing a wireless network, such as, for example:

[0291] - a wireless communication network structured according to a type of mesh other than that described in relation to Figs 1 and 9 or a star-structured wireless communication network, according to which several nodes implementing the method of modifying a configuration are connected to the same node (for example the controller node implementing the control method) or a wireless communication network supervised by a system of distributed controllers or by a remote controller hosted in a network having a cloud architecture (from the English, "cloud computing"). The mechanisms which have just been described apply in the same way,

[0292] - a heterogeneous network, in which some nodes implement the method of modification of a previously described configuration and others not. In this case, a node that does not implement the proposed solution will not renegotiate its established connections with other nodes in the network, upon request from the controller node, before and after the execution of a scheduled control action.

[0293] The embodiments that have just been presented, as well as their variants, each have numerous advantages. The proposed solution allows in particular access equipment to wireless networks connected to each other by multi-link connections, to modify upstream and then reestablish downstream the configurations of their connections to avoid disturbances caused by a control action programmed at the level of one or more of these access equipments on a frequency band used by one of the links of the connections. The solutions offered by several embodiments operate with standard messages of the IEEE 802.11 and EasyMesh standards as mentioned above.

Claims

Claims

1. Method for managing a configuration of a plurality of nodes of a wireless communication network (MN) controlled by a controller node (CTR), said nodes of the plurality of nodes being configured to establish between them connections, called multi-links, comprising at least two links using at least two distinct frequency bands, said method comprising the steps of: - obtaining (30) information relating to a control action (CA) on one of said frequency bands, programmed to be executed by at least one of said node, called executing node;- transmission (34), to at least one node, called the impacted node, of the plurality of nodes, comprising said at least one executing node, said impacted node having established at least one multi-link connection with at least one other node of said plurality of nodes, at least one link of which, called the impacted link, uses said frequency band on which the control action is programmed, of a request for modification of the configuration of said at least one connection, for the impacted link, said modification of configuration being a function of said control action; and - upon receipt (35), from said at least one impacted node, of a confirmation of modification of the configuration of said at least one connection, transmission (36) to said controller node of information indicating that said control action programmed on said frequency band is ready to be executed.;

2. Method according to the preceding claim, characterized in that it further comprises the steps of: - obtaining (37) an execution report (RP_CA) of said control action (CA) on said frequency band, received by said controller node from said at least one executing node, and - transmitting (38), to said at least one impacted node, a request (RQ2_RCFG) to reestablish the configuration of said at least one connection.

3. Method according to any one of the preceding claims, characterized in that the configuration modification request (RQ1_RCFG) of said at least one multi-link connection comprises a command to remove an authorization to transmit and receive data on said impacted link for at least one type of data flow.

4. Method according to the preceding claim, characterized in that it comprises obtaining (31) information relating to a type of configuration modification, at least as a function of the information relating to the control action, and in that, when the information relating to a type of configuration modification comprises an interruption of the data traffic on said impacted link, said command to remove an authorization to transmit and receive data on said link concerns all the types of data flows of the multi-link connection and, when the information relating to a type of configuration modification comprises a reduction of the data traffic on said impacted link, said removal of an authorization to transmit and receive data on said link does not concern all the types of data flows.

5. Method according to any one of the preceding claims, characterized in that it further comprises obtaining (33) a list (L_IMP) of said nodes impacted by said control action (CA), said list comprising said at least one executing node and at least one other node connected to said at least one node equipment by a multi-link connection comprising said impacted link, and in that the request for notification of modification of configuration of said link is sent to the impacted nodes of said list.

6. Method according to the preceding claim, characterized in that it further comprises the step of obtaining (32), from the plurality of nodes of said network, information (RSSI) relating to a level of radio signal received from neighboring nodes, and in that the list of nodes impacted by said programmed control action (CA) is determined at least from said information received and a minimum threshold (TH) of radio signal level received.

7. Method for processing a request to modify a configuration of a node to a wireless communication network, said wireless communication network comprising a plurality of nodes, said nodes of the plurality of nodes being configured to establish between them connections, called multi-links, comprising at least

8. two links using at least two distinct frequency bands, said wireless communication network being controlled by a controller node (CTR), said method comprising the steps of: - obtaining a request (RQ1_RCFG) for modification of the configuration of said at least one multi-link connection, established by the node with at least one other node of said wireless communication network, said request having been received by said node from a controller node of said wireless mesh network, said request comprising a command for deleting an authorization to transmit and receive data on the link using a given frequency band, for at least one type of data flow, - triggering the transmission (52) by said node to said at least one other node of a first request (RQ1_CNX) for renegotiation of said connection, implementing said command for deleting an authorization for transmission and reception of data on said link for said at least one connection, for the at least one type of data flow, and - following the renegotiation of said connection, triggering the transmission (54) by said node of a message comprising a report of execution of the configuration modification to the controller node. Method according to the preceding claim, characterized in that it further comprises the steps of: - obtaining a request (RQ2_RCFG) for reestablishing the configuration, received by said node from the controller node, said request comprising a command for adding an authorization for transmitting and receiving data on said link for said at least one connection, for said at least one type of flow, - triggering the transmission (56) by said node, to the at least one other node, of a second request (RQ2_CNX) for renegotiation of said at least one connection, implementing the command for adding an authorization for transmission and reception of

9.

10. data on said link for said at least one connection, for said at least one type of flow, and - triggering the transmission (58) by said node of a message (RP2_RCFG) comprising a report of execution of the reestablishment of the configuration of said at least one connection. Device (100) for managing a configuration of a plurality of nodes of a wireless communication network controlled by a controller node (CTR), said nodes of the plurality of nodes being configured to establish between them connections, called multi-links, comprising at least two links using at least two distinct frequency bands, said device being configured to: - obtaining information relating to a control action (CA) on one of said frequency bands, said control action being programmed to be executed by at least one node of said network (MN), called executing node; - transmitting to at least one node, called the impacted node, of the plurality of nodes, comprising said at least one executing node, said impacted node having established at least one connection with at least one other node of said plurality of nodes, of which at least one link, called the impacted link, uses said frequency band on which the control action is programmed, a request for modification of the configuration of said at least one connection, for the impacted link, said modification of configuration being a function of said control action; and - Upon receipt, from said at least one impacted node, of a confirmation of modification of the configuration of said at least one connection, transmit to said controller node information indicating that said control action programmed on said frequency band is ready to be executed. Device (200) for processing a request to modify a configuration of a node of a wireless communication network (MN) comprising a plurality of nodes connected to each other by connections, called multi-links, comprising at least two links using distinct frequency bands, said network being controlled by a controller node (CTR), said node having established at least one connection with another node of said network, said device being configured to: - obtaining a request (RQ1_RCFG) for modification of configuration of at least one multi-link connection, received by said node, for the link of said plurality of links using a given frequency band from a controller node of said wireless mesh network, said request comprising a command for removing an authorization for transmission and reception of data on said link for said at least one connection, for at least one type of data flow, - triggering a transmission by said node to said at least one other node of a first request (RQ1_CNX) for renegotiation of said connection, implementing said command for deleting an authorization for transmission and reception of data on said link for said at least one connection, for at least one type of data flow, and - following the renegotiation of said connection, trigger a transmission by said node of a message comprising a report of execution of the configuration modification to the controller node.

11. Access equipment (A, B, C, D) to a wireless communication network forming a node of a wireless communication network (MN) comprising a plurality of nodes, said nodes of the plurality of nodes being configured to establish between them connections, called multi-links, comprising at least two links using distinct frequency bands, said node having established at least one said multi-link connection, comprising at least two links using the at least two distinct frequency bands, characterized in that it comprises a device (200) for processing a request to modify a configuration according to claim 10.

12. Access equipment (A), called executing node, according to the preceding claim, characterized in that it is further configured to: - receive, from a controller node of said wireless communication network (MN), a command (RQ_CA) to execute a control action on one of said frequency bands, - following the execution of the control action, transmit a report (RP_CA) of execution of the action to the controller node equipment.

13. Wireless communication network (MN) comprising a plurality of nodes, said nodes being access equipment according to claims 11 or 12 and at least one configuration management device (100) according to claim 9.

14. A computer program comprising instructions for executing a method according to any one of claims 1 to 6, when said program is executed by a computer.

15. Non-volatile, computer-readable recording medium on which the computer program according to the preceding claim is recorded.

16. A computer program comprising instructions for executing a method according to any one of claims 7 to 8, when said program is executed by a computer.

17. Non-volatile, computer-readable recording medium on which the computer program according to the preceding claim is recorded.

Images