WO2011144845A1

WO2011144845A1 - Administration of a wireless meshed network

Info

Publication number: WO2011144845A1
Application number: PCT/FR2011/051071
Authority: WO
Inventors: François JAN; Daniele Miorandi; Roberto Riggio; Matteo Gerola
Original assignee: France Telecom
Priority date: 2010-05-21
Filing date: 2011-05-13
Publication date: 2011-11-24

Abstract

Method of administration executed by an item of equipment (2, 3) intended for communicating with a plurality of items of equipment (2, 3) of a wireless meshed telecommunication network (1), said method comprising a step of configuring said item of equipment comprising an allocation, to said item of equipment, a status chosen from among the status pertaining to a source of administrative information relating to said wireless meshed network and the status pertaining to a collector of said administrative information, characterized in that said configuration step comprises: a step of waiting for the reception of status messages originating from at least one item of equipment of said plurality of items of equipment, and a step of determining the status to be allocated to said item of equipment as a function of status messages received, if any.

Description

ADMINISTRATION OF A WIRELESS MESH NETWORK

Background of the invention

The invention relates to the general field of telecommunication networks and more particularly to the administration of a wireless mesh network.

A wireless mesh network ("Wireless Mesh Networks") includes fixed or mobile nodes connected to each other by wireless links. These nodes act as routers. A routing protocol is used to establish and update paths between the different nodes of the network. Communication between a source node and a destination node may pass through a plurality of intermediate nodes, in a path determined by the routing protocol.

A first type of wireless mesh network includes an infrastructure of fixed nodes connected to a transport network, wired or not, providing Internet access or other service to mobile nodes connected to these fixed nodes. In this first type of network, the communications are mainly to or from the mobile nodes, allowing data exchange on multi-hop paths. The fixed node infrastructure provides connectivity in the network.

A second type of wireless mesh network is called ad hoc network. This type of network is composed of mobile nodes. A mobile node is a node that moves or is likely to have a mobility. For this type of network no infrastructure exists, the nodes are both routers and terminals.

In both cases, the topology of the network can be modified by the appearance, disappearance or dysfunction of a node. In addition, in a wireless mesh network, the nodes generally operate with significant bandwidth constraints, and may experience significant variations in signal quality.

To account for these particularities of wireless mesh networks, K. Ramachandran, E. M. Belding-Royer, and K. C. Almeroth, "DAMON: A Distributed Architecture for Multi-hop Monitoring Mobile Networks," in Proc. Of IEEE SECON, Santa Clara, Calif., USA, 2004 (DAMON document below) provides a distributed architecture for administering a mesh network. This document explains that the administration of the network from a centralized administration node, for example according to the SNMP protocol, for "Simple Network Management Protocol", is not appropriate for a wireless mesh network. Indeed, the centralized administration node can become unreachable, for example due to the displacement of a node or a defect on a wireless link, thus making the administration of the network impossible.

Thus, the DAMON document proposes an architecture in which certain nodes execute an agent, that is to say a first software module that generates and sends information. the wireless mesh network, and some nodes run a second software module called "Sink", or "sink", which collects administration information received from one or more agents. Thus, the nodes that execute the second software module can maintain a distributed database containing the administration information. Depending on the type of software module it runs, we can talk about an "agent" node or a "sink" node.

The number of "sink" nodes must be adapted to the number of nodes in the network. Thus, according to a first example, the DAMON document proposes to configure certain particular routers as "sink" nodes. In another example, in which it is assumed that the size of an ad hoc network remains limited, the DAMON document uses a single node configured as a "sink" node.

In both cases, if the network topology is changed, the number of "sink" nodes may become unsuitable for the size of the network. For example, if new nodes appear in the network, the number of "sink" nodes may become insufficient. If a "sink" node is moved, some "agent" nodes may no longer have a "sink" node nearby. If "agent" nodes disappear from the network, the number of "sink" nodes may become too high.

However, a number of "sink" nodes that are too weak can result in congestion of the roads to the "well" nodes and an excessive load on these nodes or even cause the impossibility for certain "agent" nodes to reach the nodes ". wells. A number of "sink" nodes that are too high leads to a traffic overload, for example because of traffic between "well" nodes intended to exchange the information of the distributed database.

Object and summary of the invention

The aim of the invention is to provide a method of administration which does not present at least some of the disadvantages of the prior art.

To this end, the invention relates to an administration method executed by a device intended to communicate with a plurality of equipment of a wireless mesh telecommunications network, said method comprising a step of configuring said equipment comprising an assignment, auditing equipment, a status selected from the source status of administration information relating to said wireless mesh network and the collector status of said administration information, characterized in that said configuring step comprises:

a step of waiting for the reception of status messages from at least one collection equipment of said plurality of equipment, that is to say of a device whose status is the collector status, said message of status indicating the collector status of the collector equipment, and

a step of determining the status to be attributed to said equipment according to any received status messages. Thanks to these characteristics, a device determines, during the configuration or maintenance step, whether it should have the collector status or the source status, depending on the status of other equipment of the mesh network. Depending on the determined status, the equipment can play a role of collector node, also called "sink", or source node, also called "agent". This way of determining a status makes it possible to adapt the number of collector nodes to the size of the mesh network, and thus to avoid excessive traffic between collecting nodes and congestion of the roads towards the collecting nodes.

It is emphasized here that a node can simultaneously act as a collector node vis-à-vis other nodes of the network and source node.

According to one embodiment, the configuration step comprises, before said waiting step, a step of sending a status request message to said plurality of devices.

This reduces the time required to receive status messages from the collector nodes. The waiting step may be shorter.

Alternatively, if no status message was received during the waiting step, or if the status message (s) received originate from equipment located on a road whose metric is greater than a predetermined threshold, the The status to be assigned determined during the determination step is the collector status.

Thus, it is ensured that the metric of the route between a source node and a collector node is less than or equal to the predetermined threshold. This helps to adapt the number of collector nodes to the size of the mesh network. The metric can correspond to a number of jumps, a loss rate, a delay, ...

According to one embodiment, said plurality of equipment comprises at least one collection equipment, that is to say equipment whose status is the collector status, and a status message from said collection equipment has been received during the collection. waiting step, the determining step comprises:

if said collecting equipment is located on a road whose metric is less than or equal to a threshold, sending an association request message to said collection equipment,

- if an association agreement message is received in response to the association request message, determining that the status to be assigned is the source status,

- If no association agreement message is received in response to the association request message, determine that the status to be assigned is the collector status.

For example, a collector node may not send a chord message when it already manages a maximum number of source nodes. This avoids congestion of the roads to the collector node.

The method of administration may comprise, after the configuration step in which the source status has been assigned to said equipment, a maintenance step comprising testing a change condition based on received status messages. A source node may select a collector node as a referent node, i.e. as a node to which it sends its administration information. The maintenance step allows the source node to change the collector node refer to itself or to itself become a collector node, to take into account changes in the topology of the mesh network.

The method of administration may comprise, after the configuration step in which the collector status has been assigned to said equipment:

a step of receiving an update message of administration information,

a step of determining a type of the administration information contained in the received message,

a step of sending an update message to collection equipment of the plurality of equipment determined according to the determined type.

Thanks to these characteristics, the administration information received must not all be transmitted to the other collection nodes of the mesh network. Traffic between collecting nodes is therefore limited.

The invention also proposes a telecommunication equipment intended to communicate with a plurality of equipment of a wireless mesh telecommunications network, said equipment comprising configuration means capable of assigning, to said equipment, a status chosen from the source status of the equipment. administration information relating to said wireless mesh network and the collector status of said administration information, characterized in that said configuration means comprises:

means for waiting for the reception of status messages from at least one collection equipment of said plurality of devices, that is to say of a device whose status is the collector status, said message of status indicating the collector status of the collector equipment, and

means for determining the status to be attributed to said equipment according to any received status messages.

The invention also provides a wireless mesh telecommunications network comprising a plurality of telecommunication equipment according to the invention above. The wireless mesh network may also include other types of equipment.

Of course, the advantages and features mentioned in connection with the method of administration also relate to the telecommunication equipment and the mesh network.

The invention is also directed to a computer program comprising instructions for executing the steps of the above administration method when said program is executed by a computer.

This program can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form, or in any other form desirable shape. The invention also relates to a recording medium or information carrier readable by a computer, and comprising instructions of a computer program as mentioned above.

The recording media mentioned above can be any entity or device capable of storing the program. For example, the medium may comprise storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording medium, for example a floppy disk or a disk. hard.

On the other hand, the recording media may correspond to a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means. The program according to the invention can be downloaded in particular on an Internet type network.

Alternatively, the recording media may correspond to an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the method in question.

Brief description of the drawings

Other features and advantages of the present invention will emerge from the description given below, with reference to the accompanying drawings which illustrate an embodiment having no limiting character. In the figures: FIG. 1 is a schematic view of a wireless mesh network embodying an embodiment of the invention,

FIG. 2 is a step diagram illustrating a step of configuring a delivery method according to one embodiment of the invention; FIG. 3 is a step diagram illustrating a procedure for selecting a method of administration according to one embodiment of the invention, and Figure 4 schematically shows a telecommunications equipment according to one embodiment of the invention.

Detailed description of an embodiment

FIG. 1 represents a wireless mesh network 1 which comprises a plurality of equipment connected by wireless links. The mesh network 1 may comprise fixed equipment 2 and mobile equipment 3, or only mobile equipment (ad hoc network). A mesh network equipment 1 can communicate with another equipment in the mesh network 1 by taking a route that may be a multi-hop route.

In the example of FIG. 1, two of the devices 2 of the mesh network 1 are connected, by wire or wireless connection, to a telecommunication network 6. The telecommunication network 6 can be for example the Internet network. An equipment 3 of the mesh network 1 can communicate with a correspondent accessible by the telecommunications network 6, through one of these devices 2 which provides a gateway function to the telecommunications network 6.

FIG. 1 also shows a terminal 4 connected to a mesh network equipment

1 by a wired link or not, a terminal 7 connected to the mesh network 1 via the telecommunication network 6, and an administration station 5 connected to the mesh network 1 via the telecommunication network 6. According to a variant not shown, the management station 5 can be connected directly to the mesh network by a wired link or not, without the intermediary of the telecommunications network 6.

In order to allow the administration of the mesh network 1, each equipment 2, 3 can execute an administration software module. More precisely :

A device may execute a software module that generates and sends management information relating to the mesh network 1. Such equipment is subsequently referred to as the source node.

An equipment can run a software module that collects administrative information from source nodes. Such equipment is called collector node.

An equipment can execute both of the aforementioned types of software modules, i.e., be both a collector node and a source node.

A device may not run an administration software module. In this case, it is neither a collection node nor a source node.

A source node has a local knowledge of the mesh network 1. It can therefore build a local database containing local information on the mesh network 1. For example, the local database contains information on the quality of the wireless links since and to the source node (received signal level, received noise level, retransmission number, packet error rate), traffic to and from the source node (number of packets sent / received, transmission time, delays ), on the network topology (geographic position of the source node, routing tables of the source node), ....

A collector node collects local information from one or more source nodes, also called administration information relating to the mesh network 1. In other words, a collector node is a referent node for the source nodes from which it collects the information. In addition, a collector node may perform local information analysis of multiple source nodes to derive more global information about the state of the mesh network 1. Each collector node may therefore construct a database containing information relating to one or more source nodes, as received from the latter, and information relating to the mesh network 1 more generally. In addition, the collecting nodes communicate with each other to exchange at least part of the information of their respective databases. Thus, the collection nodes together construct a distributed database containing administrative information on the mesh network 1. For example, the part of the information exchanged corresponds to the information relating to the meshed network 1 more generally.

A collector node builds its database using for example the Management Information Base (MIB) format of the SNMP protocol and includes an SNMP interface. Thus, an administration station 5 connected to the mesh network 1 (directly or via the telecommunication network 6) can use the SNMP protocol to communicate with one of the collection nodes and thus obtain the management information relating to the mesh network 1. As part of the SNMP protocol, the management station 5 is called "Network Management System" and the administration information is called "Managed Object".

Furthermore, a collection node also comprises an HTTP interface, for "HyperText Transfer Protocol", allowing access to its database from the terminal 4 or the terminal 7, with a WEB browser.

Thus, it is possible to administer the mesh network 1 by accessing the distributed database of the collector nodes from the terminal 4 or 7 or the management station 5. In addition, if a collector node becomes inaccessible, by For example, because of the displacement or disappearance of one of the equipment of the mesh network 1, the distributed database remains accessible thanks to the other collecting nodes. It is therefore possible to administer the mesh network 1.

Subsequently, certain aspects of the operation of collector nodes and source nodes are described in greater detail.

The number of collector nodes must be adapted to the size of the mesh network 1. Indeed, as the collector nodes exchange information to build the distributed database, a large number of collector nodes leads to high traffic. On the other hand, if the number of collector nodes is small, many source nodes must communicate with the same collector node, which can cause congestion of the routes to the collector node or an inability to reach the collector node.

A mesh network equipment 1 is considered which includes an administration program comprising a "source" software module and a "collector" software module. When starting the administration program, a configuration step makes it possible to determine whether the equipment must act as a collection node or as a source node, depending on the collector or source status of the other devices of the mesh network 1. Moreover, a node source performs a maintenance procedure that may cause it to become a collector node. Thus, the configuration step and the maintenance procedure, which are described more detailed later, make it possible to adapt the number of collecting nodes to the size of the mesh network 1.

In operation, each collector node periodically broadcasts a SINKJHELLO message which notably contains an identifier of the collector node (for example, an address in the network, for example IP), an expiration time, a sequence number and the number of source nodes. that he manages. When a node receives a SINKJHELLO message, it updates a table "Collecteurs_available" storing the information received in the SINKJHELLO message and verifies that the sequence number of the received SINKJHELLO message is greater than the sequence number of the SINKJHELLO message previously received from the node collector or if it is the first SINKJHELLO message received from this collector node. If so, the node transmits the SINKJHELLO message to its neighbors, possibly waiting for a random duration. The sequence number test makes it possible to avoid an infinite diffusion of the SINKJHELLO message.

During the step of configuring a device whose administration program has been started, the reception of SINKJHELLO messages makes it possible to determine whether the equipment must become a collecting node. The course of the configuration step is shown in FIG. 2. The configuration step begins at 10 and then proceeds to steps 11 and 12. During steps 11 and 12, the equipment waits for a predetermined time to receive messages. SINKJHELLO. For each SINKJHELLO message received, the equipment checks whether the metric associated with the route between the equipment and the collector node that initiated the SINKJHELLO message is less than a predetermined threshold. This metric can for example correspond to the number of jumps or to a quality of the road, a delay, ... In this case, the equipment updates its table "Collecteurs_available" memorizing the information received in the message SINKJHELLO. The equipment also stores the metric in the "Collectors-available" table in conjunction with the information received in the SINKJHELLO message.

In the opposite case, that is to say if the metric associated with the route between the equipment and the collecting node having initiated the SINKJHELLO message is greater than the predetermined threshold, the equipment ignores the SINKJHELLO message.

For the equipment that executes the method of FIG. 2, the received SINKJHELLO messages constitute status messages from the other equipment in the network. A node initiating the transmission of a message "SINKJHELLO" is a collector node.

After the predetermined duration has elapsed, the status to be assigned to the equipment is determined in step 13, as follows:

- If the table "Collecteurs_available" is empty, the equipment determines that it must become a collector node 2 and thus the status to be assigned is that of collector node;

- If the table "Collecteurs_available" is not empty, the equipment performs a selection procedure for choosing a collector node referent, that is to say a collector node to which it communicates its administration information. This selection procedure is now described with reference to FIG. The selection procedure starts at 20 and then, in step 21, the equipment preselects the most appropriate collector node in its "Collectors_available" table. The most appropriate sink node is the one with the best route metric between the source node and the sink node and if two sink nodes have the same route metric value, the one that is already node refer for the least source nodes. As a reminder, the message SINK_HELLO includes the number of source nodes managed by the collector node broadcasting the message. If two collector nodes have the same route metric value and handle the same number of source nodes, the device randomly presets one of the two collector nodes. Then, in step 22, the equipment sends a SINK_ASSOCIATE association request message to the preselected collector node to ask it to become its referent node.

The following step 23 is a test whose result depends on the possible response to the association request SINK_ASSOCIATE. More specifically, if the collector node responds with a SINK_ASSOCIATE_ACK agreement message, the selection procedure continues in step 24 in which the equipment determines that it must act as a source node and that the collector node selected is its referent node. If the collector node responds with a rejection message SINK_ASSOCIATE_NACK (for example because it is already referencing for a maximum number of source nodes 3 or because it encounters temporary hardware problems) or has not responded after a specified period of time , the selection procedure continues at step 25.

In step 25, if the "Collectors_available" table contains at least one collector node that has not yet been preselected, the selection procedure loops in step 21. Thus, the device selects the most appropriate collector node next in the table "Collectors_available" and repeats the steps described above by sending a SINK_ASSOCIATE request message to a new selected collector node to ask it to become its referent node.

On the other hand, if in step 25 all the collector nodes of the table have already been preselected, the selection procedure proceeds to step 26 in which the equipment determines that it must become a collecting node 2.

Thus, at the end of the selection procedure, the equipment is either a source node or a collection node. It is recalled here that a collector node also plays the role of source node.

The configuration step described above thus makes it possible to ensure that the route metric between any source node and a collector node remains below the predetermined threshold. In addition, a collection node may refuse to become a referent node for another node, which may lead this other node to become itself a collection node. Thus, the number of collecting nodes is adapted to the size of the network 1.

In a variant (not shown) of the configuration step, before steps 11 and 12, the equipment broadcasts a SINK_DISCOVERY message. When they receive the SINK_DISCOVERY message, the neighboring collector nodes respond by sending a SINK_HELLO message and the neighbor source nodes respond by sending a SINK_HELLO message for each node collector contained in their "Collectors_available" table. Thus, the SINK_DISCOVERY message constitutes a status request message that minimizes the time required to receive SINKJHELLO messages. The transmission of the contents of the "Collecteurs_available" tables by the neighboring source nodes also makes it possible to obtain the SINK_HELLO messages previously broadcast in the mesh network. According to this variant, the sending period SINKJHELLO messages can be higher, which reduces the signaling traffic in the mesh network 1. Optionally, the nodes can wait a random time before responding.

A collector node that responded with a SINK_ASSOCIATE_ACK agreement message updates a "Managed Nodes" table that includes all administered source nodes.

After the configuration step, the equipment executes the "collector" software module or the "source" software module, according to the status determined in steps 13, 24 or 26.

As previously explained, a source node that executes the source software module generates administration information that it stores in a local database, and communicates this information (automatically during a change or on request) to the collector node. referenced determined during the selection procedure of the configuration step. In addition, a source node also performs a maintenance procedure to confirm that its referent node remains available.

If the referencing node is no longer available, the selection procedure described above is executed again, which makes it possible to change the referencing node. If necessary, for example when moving or removing a collector node, the selection procedure performed as part of the maintenance procedure may cause a source node to change status and then become a collector node. The maintenance procedure is now described in more detail.

As previously explained, each collection node periodically sends a SINKJHELLO message containing, in particular, an expiration time. When it receives such a message, a source node updates its table "Collecteurs_available", including by storing a time of receipt of the SINKJHELLO message and the specified expiration time. The expiration time indicated in a message SINKJHELLO is for example twice the period of sending messages SINKJHELLO.

By comparing the instant of receipt of the message, the expiration time and the current time, a source node can determine whether a collector node stored in its "Collectors_available" table can be considered valid or not. For example, a source node can periodically browse its "Collectors_available" table and remove collector nodes that are no longer available. If the referencing node is no longer available, the selection procedure is performed again. It can cause the source node to choose another referencing node or to become itself a collecting node. Thus, after the configuration step, the maintenance procedure makes it possible to change the status of a node. This therefore makes it possible to adapt the number of collecting nodes, for example in the event of a change in the topology of the mesh network 1.

With the SINK_HELLO messages, each collector node is aware of the other collector nodes of the mesh network 1. As explained above, the collector nodes also communicate with each other to build a distributed database. For this purpose, each collection node establishes a connection with each of the other collection nodes. This connection is in acknowledged mode. This is for example a TCP connection for "Transfer Control Protocol". In order to maintain a level of communication between the different collection nodes, a "keep alive" mechanism is implemented. Each connection remains open as long as the node remains in the collector status.

However, in order to limit the traffic between collecting nodes, not all the administration information contained in the own database of a collector node is transmitted to all the other collector nodes.

More specifically, a collection node receives messages containing management information relating to the mesh network 1, originating from the source nodes for which it is referencing node. The collector node updates its own database from received messages and information determined by itself. Specifically, if the administrative information has been changed, the collector node updates it in the database and increments a revision counter.

Furthermore, for each administration information (each "Managed Object") of the received message, the collector node determines whether it is a global type information or local type. For example, the collector node comprises a configuration table indicating, for each administration information that can be received, whether it is global or local type information.

When a global type of administration information has been updated in the database, the collector node then sends a message to the other collector nodes of the mesh network 1 via the connections established for each to update. its own database.

For local type administration information, the collector node sends a message to some of the other collector nodes, for example the two closest ones in the sense of the metric used.

The distributed database consists of all the databases of the collecting nodes. The global type administration information is replicated in each collector node, while the local type administration information is stored by only some of the collector nodes. In addition, the multiplicity of the collection nodes makes it possible to guarantee the safeguarding of the administration information by replication of the information between collecting nodes. Since the local type administration information is not transmitted to all the collection nodes of the mesh network 1, the traffic generated for the construction and maintenance of the distributed database remains limited. In addition, if a collector node is deleted or moved, it is likely, following the maintenance procedure described above, that at least a portion of the source nodes for which it was refer node choose as a new node refer one of the neighboring collector nodes. . Since these nodes already contain the local type administration information from these source nodes, the traffic can also be limited.

As previously explained, a network administrator may use a management station 5 or a terminal 4 or 7 to communicate with a collection node and obtain administration information.

More specifically, if a collector node receives a message from the terminal 4 or 7 or from the management station 5 and requesting the value of an administration information of global type or of local type but stored by the collector node, the Collector node can respond directly with a message indicating the requested value.

If a collector node receives a message from the terminal 4 or 7 or from the management station 5 and requesting the value of a local type of administration information and which is not memorized by the collector node, it can send a message to the collector node that stores this information to obtain the value before responding. The "Managed Nodes" table comprising all the managed source nodes makes it possible to link the collector node to the information sought.

In either case, all administration information in the distributed database is accessible to the network administrator.

Each of the devices 2 and 3 presents the hardware architecture of a computer. Thus, as shown in FIG. 4, a device 2 or 3 comprises in particular a processor 31, a read-only memory 32 in which programs are stored, a random access memory 33 used by the processor 31 to execute the programs of the read-only memory 32, and a communication unit 34 allowing the equipment 2 or 3 to receive and transmit messages.

Claims

A method of administration performed by a device (2, 3) for communicating with a plurality of devices (2, 3) of a wireless mesh telecommunications network (1), said method comprising a configuration step of said equipment comprising an allocation to said equipment of a status selected from the source status of administration information relating to said wireless mesh network and the collector status of said administration information, characterized in that said configuring step comprises:

a step of waiting (11, 12) for the reception of status messages from at least one collection equipment of said plurality of equipment, that is to say of a device whose status is the status collector, said status message indicating the collector status of the collector equipment, and

a step of determining (13) the status to be assigned to said equipment according to any received status messages.

The method of administration of claim 1, wherein the configuring step comprises, prior to said waiting step, a step of sending a status request message to said plurality of devices.

3. Administration method according to one of claims 1 and 2, wherein, if no status message was received during the waiting step, or if the status message or messages received from equipment located on a road whose metric is greater than a predetermined threshold, the status to be assigned determined during the determining step is the collector status.

The method of administration according to claim 1, wherein said plurality of devices comprises at least one collection equipment and a status message from said collection equipment has been received during the waiting step, the determining step comprises :

if said collection equipment is located on a road whose metric is less than or equal to a predetermined threshold, sending an association request message to said collection equipment,

The administration method according to claim 1, comprising, after the configuration step in which the source status has been assigned to said equipment, a maintenance step comprising testing a change condition based on received status messages. .

6. Administration method according to claim 1 comprising, after the configuration step in which the collector status has been assigned to said equipment:

a step of receiving an update message of administration information,

7. Telecommunication equipment (2, 3) for communicating with a plurality of equipment (2, 3) of a wireless mesh telecommunications network (1), said equipment comprising configurable means for assigning to said equipment , a status selected from the source status of administration information relating to said wireless mesh network and the collector status of said administration information, characterized in that said configuration means comprise:

A wireless mesh telecommunications network (1) comprising a plurality of telecommunications equipment (2, 3) according to claim 7.

9. Computer program comprising instructions for executing the steps of the administration method according to one of claims 1 to 6 when said program is executed by a computer.

Computer-readable information carrier having instructions of a computer program according to claim 9.