Method for managing nodes in a wireless communication network; method for processing a request to modify a connection configuration between the corresponding nodes, devices, and 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 said node, said executing node; sending (34), to at least one node, said impacted node, of the plurality of nodes, including 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 to modify 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 affected node, of a confirmation of a configuration change of said at least one connection, transmission (36) to said controller node of information indicating that said programmed control action on said frequency band is ready to be executed. Figure 3;

Description

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

[0001] The invention relates to the technical field of wireless communication networks and, more specifically, to access equipment, or access points, for wireless communication networks, which are interconnected by a plurality of links implementing distinct frequency bands. It relates in particular to adapting a connection configuration between two access devices when a control action likely to disrupt communications on one or more of these frequency bands via this connection must be performed. Prior art

[0002] A solution is known from the IEEE802.1 Ibe wireless communication standard, of the IEEE802.1 family, standardized by the IEEE and adopted by the Wi-Fi alliance under the name Wi-Fi 7, which allows devices to be connected 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] The standard called EasyMesh, also standardized by the Wi-Fi Alliance, is also known as a solution for deploying and managing a wireless mesh network that connects Wi-Fi access point devices potentially produced by different manufacturers. It is based on a set of transactions between these access points, which form nodes in this mesh network, typically a controller node and agent nodes. According to this solution, the agent nodes register with the network's controller node to be configured by it. The controller node has a global view of the network, as it knows both the configuration and the status of each agent in the network.

[0004] In the context of managing such a wireless mesh network, the controller node regularly triggers the execution of various control procedures or actions at the level of one or more agent nodes, and more specifically at one or more of the frequency bands they use to communicate with each other. These actions affect the node and the connections it has established with other nodes.

[0005] Such actions are therefore likely to disrupt communications between node equipment, to varying degrees, with varying degrees of impact. Examples, though not exhaustive, include:

[0006] - a procedure for analyzing or scanning a frequency band or Wi-Fi Scan, A Wi-Fi scan 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 across 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 them, such as their name or SSID (Service Set Identifier), signal strength, channel, security mode, and so on. It's important to understand that during this frequency band scanning operation, the device cannot transmit or receive data on that frequency band. For a complete scan across a sufficiently wide frequency band, the scan time can last several seconds.

[0007] - a procedure for verifying the availability of a Wi-Fi channel or Wi-Fi CAC (from the English "Channel Availability Check"), which is a specific feature of the Wi-Fi protocol, is designed to help regulate concurrent access to a given 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 ongoing transmissions 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. One specific use of this Wi-Fi CAC procedure is in preparation for switching to a radar-protected channel.According to official regulations covering a portion of the radar frequency band around 5GHz, any device wishing to use this protected part of the frequency band must first passively listen for any potential radar signals for at least one minute before transmitting its own radio signals; that is, implement the Wi-Fi CAC procedure. It cannot transmit or receive during this time.

[0008] - a Wi-Fi sensing procedure, which consists of to transmit continuously over a period of time to perform variation analysis on the reception of data packets. This action uses standard Wi-Fi packets, but with a high transmission 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, however, saturates the radio channel and is likely to disrupt the transmission or reception of certain types of data streams, particularly those associated with high latency and packet loss constraints, such as real-time (or "live") data streams like video or voice. Furthermore, this Wi-Fi sensing procedure involves not only the agent node that triggers the action by transmitting data to another node on a given link of the connection it has established with it, but also that other node, which must respond to the data it received from the agent node. The Wi-Fi sensing action therefore involves two nodes of the wireless network simultaneously.

[0009] One drawback of these control actions on the access points / nodes of the mesh network is that they disrupt communications via the connections established between them, to varying degrees, with a greater or lesser impact on the quality of service experienced by 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 agent nodes and their connections with other agent nodes, which may be impacted by the execution of one of these control actions, in order to avoid or at least limit 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 in a wireless communication network controlled by a controller node is proposed, said nodes of the plurality of nodes being configured to establish connections between them, called multi-link connections, 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, said executing node; - the transmission, to at least one node, referred to as the impacted node, of the plurality of nodes, including 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, referred to as the impacted link, uses said frequency band on which the control action is programmed, of a request to modify the configuration of said at least one connection, for the impacted link, said configuration modification being a function of said control action; and - upon receipt, from said at least one affected node, of a confirmation of a configuration change of said at least one connection, transmission to said controller node of information indicating that the said programmed control action on the said frequency band is ready to be executed.

[0012] The proposed solution is based on a completely new and inventive approach to controlling the agent nodes of a wireless network by a controller node. This approach involves anticipating the disturbances caused by the execution of a control action on one or more nodes of the wireless network by instructing them to modify the configuration of their multi-link connections that will be impacted by this control action, before the action is executed. One advantage is that the controller node inherently possesses knowledge of the connections established by each node 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 requested configuration modification depends on the programmed control action, and the nodes to which it applies depend 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 process is implemented by the controller node. Alternatively, it is implemented by a management device that can be integrated into the controller node or connected to it by means of communication.

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

[0016] It applies particularly, but not exclusively, 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, linked 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 process further comprises the steps of:

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

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

[0020] Once the control action has been executed, the controller node commands at least one affected node to restore its connection configurations. In this way, it restores its connections to the state they were in before the execution of the control action by the executing node.

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

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

[0023] According to one or more embodiments, the method includes obtaining information relating to a type of configuration change, at least based on information relating to the control action and, where the information relating to a type of configuration change includes an interruption of data traffic on said impacted link, said command to remove an authorization to transmit and receive data on said link concerns all types of data flows of the multi-link connection and, where the information relating to a type of configuration change includes 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.

[0024] For example, for a control action such as scanning a given frequency band to check the availability of a given frequency band, the configuration modification consists of completely interrupting traffic on the affected link. Conversely, for a control action such as analyzing variations in received data on a given frequency band (Wi-Fi sensing), data traffic can only be reduced by removing the use of the affected link for certain types of data streams.

[0025] For example, the type of stream concerned by this deletion is a type of stream associated with strong latency constraints, for example a real-time stream 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 equipment node by a multi-link connection including said impacted link, and in that the request for notification of configuration change of said link is issued to the impacted nodes of said list.

[0027] One 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 that is the subject of the control action or only types of flows that support the generated disturbance.

[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 level of radio signal 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 instructs the plurality of agent nodes in the wireless communication network to implement a neighbor reporting procedure, such as that defined, for example, 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 about the received radio signal level. The agent node compiles this information into a structured neighbor report, which it transmits to the controller node.

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

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

[0032] According to a second aspect, a method for processing a request to modify the configuration of a node in 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 connections, called multi-link connections, 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 configuration modification request for 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 authorization to transmit and receive data on the link using a given frequency band, for at least one type of data stream, - triggering the transmission by said node to said at least one other node of a first request to renegotiate said connection, implementing said command to remove authorization to transmit and receive 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, triggering the emission by said node of a message including a report of execution of the configuration modification to the controller node.

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

[0034] According to one or more embodiments, the process further comprises the steps of: - obtaining a configuration restoration request, received by said node from the controller node, said request including a command to add authorization to transmit and receive 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 at least one other node, of a second renegotiation request for said at least one connection, implementing the command to add authorization to transmit and receive data on said link for said at least one connection, for said at least one flow type, and - triggering the emission by said node of a message including an execution report of the restoration of the configuration of said at least one connection.

[0035] Restoring the initial configuration is implemented in a similar manner, allowing the node to recover the state of its connections with other access points before reconfiguration. Advantageously, this configuration restoration procedure occurs 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 change 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 includes information indicating a list of links authorized for said at least one connection.

[0038] In this way, the list included in the first, or second, query respectively, replaces the previously applicable list of allowed links. Thus, it is sufficient to remove the link to be deleted for at least one data stream from the list in the first query and to add it back to the list in the second query.

[0039] According to a third aspect, a device for managing a configuration of a plurality of nodes in a wireless communication network controlled by a controller node is proposed, said nodes of the plurality of nodes being configured to establish connections between them, called multi-link connections, 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, said executing node; - to send to at least one node, called the impacted node, of the plurality of nodes, including 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 to modify the configuration of said at least one connection, for the impacted link, said configuration modification being a function of said control action; and - upon receipt, from said at least one affected node, of a confirmation of a configuration change of said at least one connection, send to said controller node an 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, together 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 process according to the first aspect, in its various embodiments.

[0042] According to a fourth aspect, a device for processing a request to modify the configuration of a node in a wireless communication network comprising a plurality of nodes connected to each other by connections, known as multi-link connections, 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: - to obtain a configuration modification request for 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 including a command to remove authorization to transmit and receive data on said link for said at least one connection, for at least one type of data stream, - trigger an issuance by said node to said at least one other node of a first renegotiation request for said connection, implementing said command to remove authorization to transmit and receive 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 the transmission by said node of a message including a report of the execution of the configuration modification to the controller node.

[0043] According to at least one embodiment, the aforementioned processing 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, together 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 process according to the second aspect, in its various embodiments.

[0045] According to a fifth aspect, a wireless communication network access equipment 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 connections between them, called multi-link, 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 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 is referred to as the executing node and is further configured to: - 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 the 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 can be embedded in a control node device. The control node can be one of the access node devices of the network. Alternatively, it can be distributed among the plurality of access devices forming the nodes of the wireless communication network.

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

[0050] According to a seventh aspect, a computer program is proposed, comprising instructions for the execution of a process according to the first aspect, when said program is executed by a computer.

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

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

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

[0054] Other features and advantages will become apparent upon reading the detailed description that follows, for which reference should be made to the attached drawings, among which:

[0055] [Fig.1] 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 access equipment for wireless communication networks, according to a particular non-limiting embodiment;

[0056] [Fig.2] schematically illustrates an example of paths taken by data packet flows 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 process for managing a plurality of nodes of a wireless network, according to a particular non-limiting embodiment example;

[0058] [Fig.4] details in the form of a logic diagram 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 embodiment example;

[0059] [Fig.5] presents in the form of a flowchart the steps of a process 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 embodiment example;

[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] shows the message flows exchanged between a controller node and a wireless network node to modify the configuration of a multi-link connection established by that node, before the execution of a programmed control action of the Wi-Fi Scan type, according to a particular non-limiting embodiment;

[0062] [Fig.8] schematically illustrates an example of paths taken by data packet flows 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 embodiment;

[0063] [Fig.9] schematically illustrates the impact zones of nodes on other nodes of a wireless network, according to a particular non-limiting 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 embodiment;

[0065] [Fig. 11] schematically illustrates an example of paths taken by data packet flows exchanged via multi-link connections between 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 embodiment;

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

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

[0068] [Fig.12C] 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 the material structure of a control device, or of a modification of a configuration, according to one or more embodiments of the invention. Description of the implementation methods

[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, functionalities, and operation of computer systems, devices, processes, and program products according to one or more embodiment examples. Each block in a block diagram or each phase in a flowchart can represent a module or a portion of software code comprising instructions for implementing one or more functions. In some implementations, the order of the blocks or phases can be changed, or the corresponding functions can be implemented in parallel.

[0072] The embodiments that will now be described are, without limitation, situated within the context of networks conforming to the 802.11 family of standards of the Institute of Electrical and Electronics Engineers (IEEE), or so-called 'Wi-Fi' type networks. Examples of embodiments may be situated, for instance, within the context of the IEEE 802.1 Ibe amendment, in its D4.0 or D5.0 versions, or in its subsequent or final versions. Other embodiments may also be situated, for instance, within the context of an IEEE 802.11 standard version or an amendment to this 802.11 standard incorporating the IEEE 802.1 Ibe amendment, such as the IEEE 802.1 Ibf D3.0 amendment or the IEEE 802.11bn amendment. They apply to both home wireless networks and business networks.

[0073] In what follows, we consider in particular access equipment or access points (in English, “Access Point”), that is to say, a hardware device that allows Access points allow devices, such as user terminals like laptops, smartphones, tablets, etc., or connected objects (IoT, Internet of Things), to connect to the local area network (LAN, Local Access Network) via a wireless connection. Such an access point creates a wireless local area network within a defined area, providing radio coverage for nearby devices. It is typically connected to a wide area network (WAN, Wide Access Network), for example, a wired network, and acts as a gateway between the devices and the wired network, enabling them to communicate with other devices connected to the WAN and access the internet if the access point is connected to an internet router.

[0074] More specifically, with regard to [Fig. 1], a plurality of interconnected access devices are considered, forming nodes of a wireless MN network. In this example, the network has a mesh structure and forms a mesh network. Of course, other structures can be considered, such as a star topology.

[0075] In this example, an access device A to a wireless local area network (LANA) is connected via a multi-link (MLO) 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 protocol incorporating the IEEE 802.1 lax-2021 amendment and the Wi-Fi 7 protocol incorporating the IEEE 802.11be amendment, respectively 2.4GHz, 5GHz and 6GHz.

[0076] The IEEE 802.1 Ibe variant, also known and referred to below as Wi-Fi 7, defines the concept of a multi-link connection and the messages used to establish and manage such a connection. The Wi-Fi 7 standard allows a connection to be established between two devices on a given frequency band, and then negotiates transmission modes on other frequency bands common to both devices so that they can transmit and receive data on the different frequency bands simultaneously. It also allows for real-time negotiation of the frequency bands or links to be used to transmit and receive data via this connection.

[0077] In the example in [Fig. 1], access equipment B is itself connected to access equipment C to a local area network (LANC) via a multi-link connection (CBC) and to access equipment D to a local area network (LAND) via a multi-link connection (CBD). Finally, access equipment C is connected via a multi-link connection (CDE) to access equipment E to a local area 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] By way of purely illustrative example, a user terminal UA connected to the local area network LANA, a user terminal UB connected to the local area network LANB, a user terminal UC connected to the local area network LANC, a user terminal UD connected to the local area network LAND, and a user terminal UE connected to the local area network LANE are shown. UA-UE user terminals (or stations or STAs in the terminology of one of the standards in the IEEE 802.11 family) are, for example, a smartphone, a computer, a tablet, or a connected device.

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

[0081] Thus, in the MN mesh network of [Fig. 1], each AE node implements the Wi-Fi7 standard on the three frequency bands 2.4 GHz, 5 GHz, and 6 GHz, as well as the EasyMesh standard (for example, versions or revisions 5.0, and later versions 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 three links of their respective connections. In [Fig. 2], the packet flows exchanged on different paths between nodes AE are represented by arrows. Solid arrows denote L1 links using the 2.4 GHz frequency band, long dashed arrows L2 links using the 5 GHz frequency band, and short dashed arrows L3 links using the 6 GHz frequency band.

[0083] The fl streams of data packets exchanged between A and C through the L1 link follow 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 can be 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 CTR controller node of [Fig. 1] is configured to program and trigger the implementation of a control action on any node(s) of the MN mesh network, including itself. For example, this control action is one of the procedures described previously, including: - the procedure for analyzing or scanning a frequency band, or Wi-Fi Scan, - the procedure for checking the availability of a Wi-Fi channel or Wi-Fi CAC, and - the detection procedure or Wi-Fi Sensing.

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

[0094] Such a control action is likely to cause more or less severe disturbances to the data packet flows 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 users of the wireless communication networks of the node and the other impacted nodes.

[0095] The following are presented devices and methods for controlling and modifying a connection configuration established by the executing node with other nodes of this wireless mesh network (MN), before the executing node implements a frequency band control action that could cause disturbances in the data packet flows exchanged by the node on the links of the connections established by that node using that frequency band. These devices and methods make it possible to anticipate the disturbance(s) by adapting the configurations of the connections concerned in advance.

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

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

[0098] - trigger the transmission by the controller node, destined for 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, said at least one connection comprising at least two links using distinct frequency bands among which one link, said impacted link, uses said frequency band on which the control action is to be executed, of a configuration modification request of said at least one multi-link connection, for the impacted link, said configuration modification being a function of said control action, and,

[0099] - upon reception by the controller node, from said at least one node impacted, of a confirmation of modification of the configuration of said at least one connection, send to said controller node an 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 multiple nodes of a wireless network, which will be described below in relation to [Fig. 4]. The device 100 can be implemented in various ways, both software and / or hardware. An example of the 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 MN mesh network comprises a device 200 for processing a request to modify the 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: - to obtain a configuration change request for at least one connection for the multi-link connection using a given frequency band, received by said node from the controller node of said wireless network, said notification including a command to remove authorization to transmit and receive data on said link for said at least one connection, for at least one type of data stream, - trigger the issuance by said node to said at least one other node of a first renegotiation request for said connection, implementing said command to remove authorization to transmit and receive 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 the issuance by said node of a message including a report of the 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 connection configuration, which will be described below in relation to [Fig. 5]. The device 200 can be implemented in various ways, both software and / or hardware. An example of the hardware structure of the device 200 will be described below in relation to [Fig. 13].

[0103] A method for managing a plurality of nodes in a wireless communication network is now presented in relation to [Fig. 3]. In the following, the method is considered to be implemented by a device integrated into a controller node, which can be any one of the nodes in 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, for example, be 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.1], 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 includes at least an identifier of the control action CA and an identifier of the node(s) that are to execute it. Optionally, it may also include additional information relating, for example, to a type of disturbance generated 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 change, at least as a function of the ICA information relating to the control action.

[0107] Depending on the CA control action to be executed, the type of configuration change 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 type of modification 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 CA control action identifier which is then used as a search index to access additional information elements which are stored in memory, for example device 100 or controller node CTR.

[0109] Depending on the CA control action programmed to be executed, nodes other than the executing node 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 in 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 TH threshold level. This RSSI information is obtained in step 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 upon request.

[0111] This second option allows the current state of the MN network to be taken into account and is illustrated by [Fig.4]. Device 100 triggers the sending by the CTR controller node, at 321, of a neighborhood report request to certain nodes of the plurality of nodes of the MN mesh network.

[0112] This Neighbor Report request instructs the receiving node to listen to a given frequency band, typically the one targeted by the programmed control action, and to determine, for each detected radio signal, information relating to a Received Signal Strength Indication (RSSI). For example, the node implements a Neighbor Report procedure as specified by the IEEE 802.1k-2008 standard, which allows a Wi-Fi access point (AP) to collect information about neighboring access points and which works as follows: - The node sends a Neighbor request to other neighboring APs to obtain information about their networks and capacities, - Neighboring nodes respond to the request with a Neighbor Response that includes information about their identity and capacity, notably the different frequency bands they are able to use, - The node listens to the given frequency band and determines, for each radio signal received from another access point, typically a beacon frame, an RSSI (Return Status Information) value. - 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] Device 100 obtains the neighborhood reports received by the controller node from the relevant nodes of the MN network in 322.

[0114] Device 100 is configured to use RSSI information received from one node out of a plurality of access point nodes to determine a range measurement for each of them. To do this, at 323 it selects a current node NC and, for each RSSI information contained in its neighbor report, it uses at 324 a given threshold TH, for example, set to -75dBm, and compares the value of this RSSI information for the 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 is occupying 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 performs a control action on the frequency band, the current node NC will potentially be affected.

[0115] 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 TH threshold, it considers the neighboring node not to be "visible" to the current node and moves on to the RSSI information received from another neighboring node by the current node. It repeats this operation for all RSSI information in the neighborhood report of the current node.

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

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

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

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

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

[0121] In particular, when the configuration change type T_M0D includes a reduction of the connection on the impacted link, the configuration change request for said at least one connection includes a notification of the removal of an authorization to transmit and receive data on said impacted link for at least one type of data flow.

[0122] Conversely, when the configuration change type T_MOD includes an interruption of the connection on the impacted link, the configuration change request for said at least one connection includes a notification of the removal of an authorization to transmit and receive data on said impacted link for all types of data flows.

[0123] For example, for a CA control action such as a Wi-Fi scan of a given frequency band or a Wi-Fi CAC (Wi-Fi Availability Check) of a given frequency band, the configuration change consists of completely interrupting traffic on the affected link. In contrast, for a control action such as Wi-Fi sensing (analyzing variation in received data on a given frequency band), data traffic can only be reduced by removing the use of the affected link for certain types of data streams.

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

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

[0126] During a step 36, the device 100 informs the controller node, for example by sending it an STRT-CA message, that the required configuration changes 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 of the end of execution of the control action by the executing node(s), for example it obtains a message including for example an execution report of the control action CA received from the controller node from the executing node.

[0128] In 38, device 100 triggers the issuance by the controller node of a message including a second request or configuration change notification RQ2_RCFG is sent to the affected nodes. It includes a request to restore the configuration of at least one connection. This message can also be sent over one or more links of the multi-link connection(s). Sending it over all links increases the likelihood of it being received by the intended node.

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

[0130] The process just described allows a controller node to synchronize a renegotiation by the node(s) of the multi-link connections that 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 can be a single message sent to all affected nodes and to which each affected node 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 containing information about a list of multi-link connections to be reconfigured and a response message sent after each of the affected nodes applies 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 specification, Wi-Fi_EasyMesh_Specification_DRAFT_R6-240208b. For example, this EasyMesh reconfiguration transaction is constructed as follows: - An "AP MLD Configuration Request message" type request (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 entitled "AP MLD Configuration Agent TLV" (specified in EasyMesh Specification R6, Section 17.2.96). More generally, a TLV information field contains "Type, Length, Value" information, 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. One advantage of a TLV information field is that it allows the addition of new types information without requiring major changes to the underlying standard or protocol.

[0134] More specifically, the "Agent AP MLD Configuration TLV" field describes connection configuration parameters, in particular the links allowed to carry 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 multi-link connection list or Multi-Link Description MLD (for "Multi- Link Description », in English), the number of which is given by the “Value” field entitled '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 equipment, the number of which is given by the 'Num' field Affiliated APs'. For each access device in this list, the "Agent AP MLD Configuration" information field includes an EasyMesh-compliant description of that access device, including an access device MAC address ("AP MAC Address"), a unique radio identifier ("Radio Unique Identifier"), and a link ID of the link in the multi-link connection.

[0141] 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 affected node responds to the controller node with a reply message. This message has two functions: first, to acknowledge the configuration change, and second, to update the configuration information of the multi-link connections at the controller node.

[0143] The "AP MLD Configuration Response message" includes the "Agent AP MLD Configuration TLV" information field detailed above, in which for each multi-link connection the relevant node 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 contents of which correspond to those of the Wi-Fi7 configuration and will be detailed below in relation to [Fig.6].

[0144] In relation to [Fig. 5], a method for processing a request to modify the configuration of a multi-link connection established by is now described. a node of a wireless network, according to one or more embodiments. In what follows, it is assumed that the method in question is implemented by a device 200 as described previously, in relation to [Fig. 1]. 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. 1], which is among the nodes identified as likely to be impacted by the control action programmed to be executed by said at least one executing node on a given frequency band. This impacted node can therefore be the executing 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 in the wireless network.

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

[0147] According to one or more embodiments, this request includes 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] In 52, the device 200 sends to said other node a message including a first RQ1-CNX request to renegotiate said connection, including 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 allowed for the transmission and reception of data streams and therefore do not include said link for said at least one data stream.

[0150] For example, configuration instructions are specified using an information field entitled "Traffic ID to Link Mapping" or "TID-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 (a "bitmap") in which each bit corresponds to a link in the multi-link connection, the corresponding link being allowed when the bit is 1 and forbidden when it is 0.

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

[0152] In 54, device 200 obtains a configuration recovery request message received by the impacted node from the controller node, including a command to add an authorization to transmit and receive data on said link for said at least one connection, for said at least one type of flow.

[0153] In 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 including a second RQ2_CNX request for renegotiation of said at least one connection, including configuration instructions, implementing the command to add an authorization to transmit and receive 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 allowed for the transmission and reception of data streams and they include said link for said at least one type of stream.

[0155] In 56, device 200 triggers the transmission by the impacted node and to the controller node of an RP2_RCFG message including an execution report of the restoration 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 once the multi-link connections 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, and then a second time, once the control action has been completed, at the request of the controller, to restore the initial configurations.

[0158] According to one or more embodiments, the connection renegotiation request messages conform to 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 device that wishes to attach to it, an access device can define information relating to one or more types of flows allowed on each of the links of this connection. This information is described in a management frame (in English, The "beacon" is a message that a station periodically transmits within its local area network (LAN) to advertise its capabilities, particularly in terms of Quality of Service (QoS), which stations and other access points then listen to. The information obtained allows a station to determine which Wi-Fi networks are available and decide which access point to connect to. The management frame includes other essential information about the local network, such as the network name (SSID - Service Set Identifier), security capabilities, supported channels, timeouts, and so on. For other access points, this information allows them to identify neighboring access points visible over the radio frequency and thus coordinate using the EasyMesh protocol.

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

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

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

[0163] In this regard, the term "Traffic Identifier" refers to any identifier that can be used by higher-layer entities to distinguish Media Access Control (MAC) service data units (MSDUs) from MAC entities that support Quality of Service (QoS) within the MAC data service.

[0164] There are 16 possible values ​​for the traffic identifier, 8 of which identify TC traffic categories (for "Traffic Categories") distinguishing 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 8 other possible values ​​identify parameterized traffic stream (TS) types, i.e., specific data stream types in a Wi-Fi network that are associated with parameters of Specific transmission parameters. These data streams 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 associated 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 OSI model layers above the MAC layer. This ensures a mapping between the IP layer (TOS / DSCP field) and the Wi-Fi MAC layer (TID) for transmission management. Once the packet is categorized, the information is embedded in the Wi-Fi header. This allows the Wi-Fi protocol to handle a category of flow independently once that flow is identified and tagged 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-to-Link Mapping identifier (TID-To-Link Mapping) takes the form of a TLV information element, the "Value" information field of which indicates, for each link in the multi-link connection, the types of traffic that can pass through that link. If no traffic type is defined for a link, it is considered that link is no longer usable. By default, all traffic types are allowed on all links.

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

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

[0170] For example, the 200 device is configured to transmit this TID-To-Link Mapping field in an action frame, as defined, for example, in IEEE 802.1 Ibe Draft 4.0, an "Action Frame". In one embodiment, this is a special type of control frame used by a node in 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 Broadband" (EHT) mode. "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] Eixed 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 link composition using a bitmask of the allowed links. In binary, 0x5 equals 101, which corresponds to L1=1, L2=0, L3=1. Therefore, link L2 is not allowed for the connection.

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

[0198] Following the example in [Fig. 6], the configuration restoration instructions are transmitted in an Extended Broadband (EHT) Link Recommendation action frame, and the "Traffic Indication List" parameter is now set to 0x7. In binary, this value corresponds to the binary sequence 111, which indicates L1=l, L2=l, L3=l. Once this configuration change is implemented, all links in the multi-link connection between nodes A and B are again authorized.

[0199] With reference to [Fig. 7], an example of implementing the methods just presented is now described where the programmed control action is a Wi-Fi Scan procedure for analyzing or scanning a given frequency band from among the available frequency bands. With reference to [Fig. 1], it is assumed that the CTR controller node has programmed the execution of this Wi-Fi Scan control action on one of the 5 GHz frequency bands, for example, the low band 5150 MHz - 5350 MHz. In the example of [Fig. 1], the CTR controller node and node A are a single access device. However, the following description applies equally well when the two nodes are separate access devices.

[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 interruption 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], device 100 of the CTR controller node obtains at 30 the ICA information relating to the scheduling of a Wi-Fi Scan type ICA control action on node A of the MN wireless network that it controls. It notifies node A by sending it at 34 an RQ1_RCFG request to modify the configuration of its CAB connection. This request indicates that the authorization to transmit and receive on the L2 link must be revoked. Device 200 of node A receives this request and initiates a renegotiation of its CAB connection with node B by sending it at 52 an RQ1_CNX connection renegotiation request in which the transmission and reception of data on the L2 link are no longer authorized, regardless of the type of data traffic.

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

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

[0207] With reference to [Fig.8], following this first renegotiation of the multi- connection CAB links have the following impact on the previously defined data packet flows: - 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 CTR controller node initiates 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 notified (END Wi-Fi SCAN), device 100 of the CTR controller node notifies node A by sending an RQ2_RCFG request at port 38 to restore the configuration of its CAB connection. This request indicates that the previously removed authorization to transmit and receive on the L2 link must be added back. Device 200 of node A receives this request at port 54 and initiates a renegotiation of its CAB connection with node B by sending an RQ2_CNX connection renegotiation request at port 55, in which the transmission and reception of data on the L2 link is again authorized regardless of the type of data traffic.Upon receiving confirmation from node B at step 56, device 200 of node A confirms at step 57 to the controller node the restoration of the initial configuration for the CAB connection.

[0215] With reference to Figures 9-11, an example of implementing the methods just described is now described in the case where the programmed control action is a Wi-Fi Sensing procedure for detecting packet reception data is transmitted over a given frequency band from among the available frequency bands. Referring to [Fig. 1], it is assumed that the CTR controller node has programmed the execution of this Wi-Fi Sensing control action on the 5 GHz frequency band between nodes A and B, which are hereafter considered both as executors, even though in the example [Fig. 1] it is A that is designated to initiate the Wi-Fi Sensing procedure and B only reacts. In the example in [Fig. 1], the CTR controller node 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 disruption duration is estimated at 10 seconds. The impact of a Wi-Fi Sensing control action can be defined as a significant reduction in transmission and reception on L2 links using the 5GHz frequency band for all connections established by both nodes A and B during the data packet exchange.

[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 5 GHz frequency band to perform the Wi-Fi Sensing action, the impact zone can be defined as all the nodes in the mesh network that use this 5 GHz frequency band and are close enough to nodes A and B to be affected by this packet exchange, i.e., to detect the resulting radio signals. For example, the proximity of one node to another can be deduced from a Received Signal Strength Indication (RSSI) provided by the node in question to the other node, and compared to a given threshold TH, for example set at -75 dBm, as previously described in relation to [Fig. 4].In this case, the nodes of the MB mesh network that 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 device 100 of the CTR controller node.

[0219] The latter can retrieve and group information concerning the received signal level RSSI by each node of 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 reporting procedure as specified in the IEEE 802.11k standard.

[0220] By way of illustrative and non-limiting example, a minimum radio signal level TH threshold of -75dBm can be considered. Thus, for a given node, all its neighbors "Visible" nodes above TH = -75dBm, meaning those whose nodes receive radio signals with a signal level exceeding the TH threshold, are considered to be impacting the network. In other examples, the given TH threshold 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 receive sensitivity of the nodes comprising the wireless network.

[0221] Thus, it is possible to determine from the neighborhood reports and the TH threshold, for each node of the mesh network, whether it is within range of an executing node; then to establish a list of nodes that will be impacted by the transmissions of the executing node, and to deduce from this a list L_IMP of the nodes impacted by the Wi-Fi Sensing action by making the union of 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 MN mesh network. 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 of the transmission from another node.

[0223] In the example considered, it is therefore 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 bidirectional 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 including 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], the message flows between the CTR controller node and the MN wireless network nodes that 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 device 100 has already performed the impact study and that it has the L_IMP list of impacted nodes, for example stored in the memory of device 100 or the CTR controller node.

[0228] Device 100 is configured to send (step 34) an initial RQ1-RCFG configuration change request to the nodes in the L_IMP list, specifically A, B, C, and D, requesting them to remove the L2 link (which uses the 5 GHz frequency band) from their connections with other nodes in the MN mesh network. For example, it sends a single message to all the affected nodes. Alternatively, it sends a message to each affected node.

[0229] Upon reception, device 200 at node A renegotiates the links to be used with node B in order to no longer use link L2 [A,B] and to use links L1 [A,B] and L3 [A,B] instead. To do this, it applies proprietary logic that may take into account the capacities of 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.4 GHz frequency band (L1) has a significantly lower capacity than the 5 GHz frequency band (L2) and even more so than the 6 GHz frequency band (L3). In this case, device 200 at node A decides to replace L2 with L3, which has the highest bandwidth.

[0230] According to one or more embodiments, the device 200 of node A sends (step 52) to 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 removed the L2 {A,B} link from the list of allowed links.

[0231] Similarly, device 200 of node B renegotiates the links to be used with node C so as to no longer use link L2{B,C] and to use links L1{B,C] and L3{B,C] instead. To do this, according to one or more embodiments, device 200 of node B sends (step 52) to 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 node APC (step 53).

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

[0233] Similarly, device 200 of node C renegotiates, in a similar way, the links to be used with node E in order to no longer use the L2{C,E] link 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 dealt with by node B.

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

[0236] At this stage, the renegotiated connections are configured as illustrated by [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 RQ1_RCFG configuration change request has been taken into account, the controller node triggers the execution of the scheduled Wi-Fi Sensing control action by sending an RQ1_CA execution request to node A.

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

[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 receiving a notification of completion (step 37), the controller node's device 200 sends (step 38) a second RQ2_RCFG configuration modification request to the affected nodes, asking them to restore the L2 link in their respective connections. To do this, it indicates, for example, that the L2 link is enabled. For example, it sends a single message addressed to all affected nodes. Alternatively, it sends a message to each affected node.

[0246] Upon receipt, node A renegotiates the links to be used with node B in order to use the L2{A,B} link again. To do this, according to one or more embodiments, the device 200 of node A sends (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 the L2{B,C] link again.

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

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

[0250] Node D has no links to renegotiate.

[0251] Next, once their connections are restored, 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] With reference to Figs 12A-12C, an example of a method for modifying a connection configuration established by the nodes of a wireless network is now described according to another embodiment. In this example, the solution based on renegotiating the use of multiple links makes it possible to specify which types of traffic, in other words, which specific data flows are allowed to use each link of the connection.

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

[0254] According to the Wi-Fi standard and as shown in the table in [Fig. 12A], these different types of flows are associated with distinct traffic IDs. For example, type BE is associated with the ID 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, a link of the connection established between A and B on the 2.4GHz frequency band allowing all types of BK, BE, VI and VO traffic is denoted as follows: L1{A,B][BK, BE, VI, VO]. If the VI type data stream is removed for this link, the notation becomes as follows: L1{A,B][1][BK, BE, VO].

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

[0257] For example, it is assumed that the CA control action programmed on the PA node of [Fig. 1] is a Wi-Fi Sensing procedure on the frequency band used by the L2 link and that the affected nodes are those defined in relation to [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, 5 GHz, may disrupt VI and VO type flows, but BK and BE type flows are not necessarily heavily impacted. In this case, the link usage must be renegotiated to perform a partial withdrawal of the affected L2 link, excluding 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 the 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 configuration change request for the connection(s) issued to the affected node(s) of the MN wireless network (L_IMP) includes a notification of the removal of authorization to transmit and receive data on said affected link for at least one type of data flow, but not for all types of data traffic. For example, it explicitly specifies that data traffic types VI and VO are not allowed to transit through the L2 link. For example, it may also specify that data traffic types VI and VO must be routed through another link of the connection, for example the L3 link, whose frequency band is not subject to a scheduled control action.

[0260] In this way, we distinguish the types of traffic, the flows more heavily impacted (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 link L2 and redirected to one of the other links.

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

[0263] For example, such an information element indicating the withdrawal of VI and VO type 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], it is understood that the line "Link Mapping Of TID 5: 0x0005" amounts to allowing VI type 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 issued by the controller node to the node(s) impacted by the control action, another TLV type information field than the one 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] Next, the device 200 of an affected node is configured to trigger a renegotiation of the multi-link connections it has established with other nodes, which may be access points or stations, by sending them a connection renegotiation request. This request may, for example, take the form of a generic control message of the action frame type, including a TID-to-Link Mapping TLV 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 affected node, for example, conforming to the EasyMesh protocol, and for a multi-link connection renegotiation request, conforming to the Wi-Fi standard, between an affected node and the stations or other access points connected to it.

[0281] In relation to [Fig. 12C], the MOD state of the multi-link connection between nodes A and B is shown after the configuration change just described. Data flows VI and VO no longer use the L2 link, but are redirected to the L3 link.

[0282] This alternative embodiment is advantageous because it allows different configurations to be specified according to the types of data traffic.

[0283] In relation to [Fig. 13], an example of the material 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 include 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 Wi-Fi 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. Device 100 may also include one or more media readers 150 for reading computer-readable storage media (e.g., a digital storage disc (CD-ROM, DVD, Blu-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] Memory 120, 220 may include random access memory (RAM), cache memory, non-volatile memory, backup memory (e.g., programmable or flash memory), read-only memory (ROM), hard disk drive (HDD), solid-state drive (SSD), or any combination thereof. The ROM of memory 120, 220 may be configured to store, among other things, a device operating system 100, 200 and / or one or more computer program codes for one or more software applications. The RAM of memory 120 may be used by the processor 110, 210 for temporary data storage.

[0286] The processor 110, 210 can be configured to store, read, load, execute, and / or otherwise process instructions stored in a computer-readable storage medium and / or in 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 control method, or configuration modification method, described in this document. Means implementing a function or 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 set of functions, as described below for the means concerned.

[0287] This description also relates to a data processor-readable information medium containing instructions for a program as described above. The information medium can be any hardware, entity, or device capable of storing the instructions for a program as described above. Usable program storage media include ROM or RAM memories, magnetic storage media such as magnetic disks and tapes, hard drives, or optically readable digital data storage media, or any combination thereof.

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

[0289] One embodiment also relates to a computer program product comprising a computer-readable storage medium on which program instructions are stored, the program instructions being configured to cause the host device (e.g., a computer, or device 100 of the controller node, or device 200 of an impacted node) to implement all or part of the steps of one or more of the processes 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, or respectively, a node access equipment of a mesh network.

[0290] The embodiments just presented are not limited to the specific example of a mesh network just presented and apply to other types of wireless communication networks whose nodes are each wireless network access devices, such as, for example:

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

[0292] - a heterogeneous network, in which some nodes implement the process 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 connections established with other nodes in the network, at the request of the controller node, before and after the execution of a programmed control action.

[0293] The embodiments just described, as well as their variants, each offer numerous advantages. In particular, the proposed solution allows wireless network access devices connected via multi-link connections to modify their connection configurations upstream and then restore them downstream to avoid interference caused by a programmed control action on one or more of these access devices in a frequency band used by one of the connection links. The solutions offered by several embodiments operate with standard messages from the IEEE 802.11 and EasyMesh standards as previously mentioned.

Claims

1. Demands A method for managing a configuration of a plurality of nodes in a wireless communication network (WCN) controlled by a controller node (CTR), said nodes in the plurality of nodes being configured to establish connections, called multi-link connections, comprising at least two links using at least two distinct frequency bands, said method implemented by a device (100) for managing a configuration of a plurality of nodes in a wireless communication network, integrated into the controller node or connected to it by a communication interface, 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 said node, said executing node, and capable of disrupting communications on one or more multi-link connections established between the executing node and one or more other nodes of the wireless communication network; - triggering the transmission (34), by the controller node to at least one node, called the impacted node, of the plurality of nodes, said at least one impacted node including said at least one executing node, and at least one other node of said plurality of nodes, with which said at least one executing node has established at least one multi-link connection, of which at least one link, called the impacted link, uses said frequency band on which the control action is programmed, of a request to modify the configuration of said at least one connection, for the impacted link, said modification of configuration being a function of said control action and including a command to remove an authorization to transmit and receive data on said impacted link for at least one type of data flow; and - upon receipt (35), from said at least one affected node, of a confirmation of a configuration change of said at least one connection, transmission (36) to said controller node of information indicating that said programmed control action on said frequency band is ready to be executed.

2. A 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 - sending (38), to said at least one impacted node, a request (RQ2_RCFG) to restore the configuration of said at least one connection.

3. A method according to any one of the preceding claims, characterized in that it comprises obtaining (31) information about a type of configuration change, at least as a function of the information about the control action, and in that, where the information about a type of configuration change includes an interruption of data traffic on said impacted link, said command to remove authorization to transmit and receive data on said link relates to all types of data flows in the multi-link connection and, where the information about a type of configuration change includes a reduction of data traffic on said impacted link, said removal of authorization to transmit and receive data on said link does not relate to all types of data flows.

4. A 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 equipment node by a multi-link connection comprising said impacted link, and in that the configuration change notification request for said link is issued to the impacted nodes in said list.

5. A 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 radio signal level received from neighboring nodes, and in that the list The nodes impacted by said programmed control action (CA) is determined at least from said received information and a minimum threshold (TH) of received radio signal level.

6. A method for processing a request to modify the configuration of a node in a wireless communication network, said wireless communication network comprising a plurality of nodes, said nodes of the plurality of nodes being configured to establish connections, said multi-link connections, comprising at least two links using at least two distinct frequency bands, said wireless communication network being controlled by a controller node (CTR), said method implemented by a modification request processing device (200) integrated in said node, comprising the steps of: - receiving a request (RQ1_RCFG) to modify the configuration of at least one multi-link connection, established by the node with at least one other node of said wireless communication network, issued by a controller node of said wireless mesh network in accordance with the method according to any one of claims 1 to 5,said request including a command to remove 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) to renegotiate said connection, implementing said command to remove authorization to transmit and receive 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, triggering the transmission (54) by said node of a message including a report of the execution of the configuration change to the controller node.

7. A method according to the preceding claim, characterized in that it further comprises the steps of:

8. - receipt of a request (RQ2_RCFG) to restore the configuration, from the controller node, said request including a command to add authorization to transmit and receive 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 at least one other node, of a second request (RQ2_CNX) to renegotiate said at least one connection, implementing the command to add authorization to transmit and receive data on said link for said at least one connection, for said at least one flow type, and - triggering the emission (58) by said node of a message (RP2_RCFG) including an execution report of the restoration of the configuration of said at least one connection. Device (100) for managing a configuration of a plurality of nodes in a wireless communication network controlled by a controller node (CTR), said nodes of the plurality of nodes being configured to establish connections, called multi-link connections, comprising at least two links using at least two distinct frequency bands, said device being integrated into the controller node or connected to it by a communication interface, said device comprising at least said communication interface, a memory, and a processor connected to said at least one communication interface and to the memory to control its operation and configured to: - obtain 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), said executing node, and likely to disrupt communications on one or more multi-link connections established between the executing node and one or more other nodes of the wireless communication network;

9. - trigger the transmission to at least one node, referred to as the impacted node, of the plurality of nodes, said at least one impacted node comprising said at least one executing node and at least one other node of said plurality of nodes, with which the executing node has established at least one connection, of which at least one link, referred to as the impacted link, uses said frequency band on which the control action is programmed, of a configuration modification request for said at least one connection, for the impacted link, said configuration modification being a function of said control action and comprising a command to remove authorization for the transmission and reception of data on said impacted link for at least one type of data flow; and - Upon receipt, from said at least one affected node, of a confirmation of a configuration change of said at least one connection, send to said controller node an information indicating that said control action programmed on said frequency band is ready to be executed. Device (200) for processing a request to modify the configuration of a node in a wireless communication network (MN) comprising a plurality of nodes connected to each other by connections, called multi-link, 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 integrated into said node, said device comprising at least one communication interface, a memory and a processor connected to said at least one communication interface and to the memory to control its operation and configured to: - receive a request (RQ1_RCFG) to modify the configuration of at least one multi-link connection, for the link of said plurality of links using a given frequency band, issued by a management device according to claim 8 from a controller node said wireless mesh network, said request including a command to remove authorization to transmit and receive data on said link for said at least one connection, for at least one type of data flow, - trigger an issuance by said node to said at least one other node of a first request (RQ1_CNX) to renegotiate said connection, implementing said command to remove authorization to transmit and receive 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 an issuance by said node of a message including a report of the execution of the configuration change to the controller node.

10. 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 connections, called multi-link, between them, 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 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 9.

11. Access equipment (A), referred to as the 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, issue a report (RP_CA) of the execution of the action to the controller node equipment.

12. Wireless communication network (MN) comprising a plurality of nodes, said nodes being access equipment according to the

13.

14.

15.

16. claims 10 or 12 and at least one configuration management device (100) according to claim 8. Computer program comprising instructions for carrying out a process according to any one of claims 1 to 5, when said program is executed by a computer. Non-volatile and computer-readable recording medium on which the computer program according to the preceding claim is recorded. Computer program comprising instructions for carrying out a process according to any one of claims 6 to 7, when said program is executed by a computer. Non-volatile and computer-readable recording medium on which the computer program according to the preceding claim is recorded.

Images