Discovery of a synchronization network within a network of equipment

Abstract

The present invention relates to a method for discovering, within a network (NET), a synchronization network comprising a set of synchronization nodes, said method being implemented by a management device connected to at least one of said synchronization nodes, comprising the steps of performing a verification (200) by means of the previously obtained clock identifier (Ck_idi+1) from one of said synchronization nodes (Ni), said clock identifier being associated with a synchronization node (Ni+1) providing synchronization information to said synchronization node (Ni) from which said clock identifier is obtained;and, depending on the result of said verification, obtaining (300) a new clock identifier from said synchronization node (Ni+1) associated with said previously obtained clock identifier, said new clock identifier being associated with a synchronization node providing synchronization information to said synchronization node (Ni+1) associated with said previously obtained clock identifier. It also relates to a corresponding management device. Figure for the abstract: Fig. 2;

Description

Title of the invention: Discovery of a synchronization network within a network of equipment Prior art

[0001] The present invention relates to the field of equipment networks in the broad sense, and more particularly the discovery of a synchronization network within such networks.

[0002] A network of equipment usually comprises a plurality of equipment connected to each other, also called network nodes, allowing the exchange of resources, information or data to be routed between these equipments, in order to provide them to a third-party network or to users.

[0003] Among these network nodes, a certain number can be used for synchronization in the network, and are used in particular to distribute synchronization information within the network, from a synchronization source equipment to a final equipment, which can be either a user terminal or a base station in the case of a telecommunications network of the mobile access network type. These can in particular be IP routers, WDM optical transmission nodes, or optical line terminals (OLT). These nodes can then be designated as synchronization nodes (or clock nodes).

[0004] This synchronization information, depending on whether it concerns phase or frequency synchronization, is vital for the proper functioning of a network of equipment in that it is necessary for certain critical operations of this network. When it comes to a mobile network, this is particularly the case for communication transfers (i.e. "handovers" in English) between base stations (requiring frequency synchronization) or the coordination of antennas operating in TDD mode (requiring phase synchronization). This is also the case for the time stamping of financial operations or transactions, or the precise supervision of electrical distribution networks.

[0005] [Fig.l] schematically illustrates the architecture of a network in which such synchronization networks are used.

[0006] The NET network illustrated in [Fig.l] thus comprises a certain number of network nodes. Among these, in addition to network nodes NN having other functions which will not be discussed here, synchronization nodes Ni are illustrated, forming between them one or more synchronization networks, within the NET network.

[0007] Thus, a first synchronization network is illustrated, in which a first synchronization node Ns, otherwise referred to as a synchronization source node, transmits synchronization information SYNCs to a first intermediate synchronization node Ns_i. This first intermediate node will in turn transmit synchronization information to another, and so on, as represented in [Fig.2] by an intermediate synchronization node Ni+i transmitting to another intermediate node N;, located “downstream”, synchronization information SYNCi+i (the variable i can take any value between 0 and S). Finally, at the end of the synchronization chain, a penultimate synchronization node Ni transmits synchronization information SYNCi to a last synchronization node No, otherwise referred to as a terminal synchronization node.

[0008] All of these nodes Ns, NS-i, ..., Ni+i, Ni,.. ., Ni and No thus form a first synchronization network. A second synchronization network is also illustrated, consisting of the synchronization nodes NS', NS” Ni+i', Nr and N0', in order to illustrate the fact that two (or even more) synchronization source nodes (NS', NS”) can be located at the source of a synchronization network.

[0009] These two synchronization networks are indicated here for purely illustrative purposes, in order to illustrate the fact that a synchronization network may consist of any number of synchronization source nodes, connected to any number of synchronization terminal nodes by means of any number of intermediate synchronization nodes, in order to distribute synchronization information from the source node(s) to the terminal node(s) of such a network.

[0010] In the specific case of a telecommunications network, a synchronization network as illustrated in [Fig.l] may in particular comply with the IEEE 1588 standard. In particular, the PTP profile ITU-T G 8275.1 of this standard may be used for the transport, in the form of PTP packets, of phase synchronization information (which may also be referred to as "phase reference information" since it allows each synchronization node receiving such information from a parent node to synchronize with the parent node, and thus to synchronize all the nodes step by step) from a synchronization source equipment to a synchronization terminal equipment, which may be a 5G antenna in the case of a fifth generation mobile access network.

[0011] In such a synchronization network conforming to the IEEE 1588 standard, the synchronization source node Ns is then designated as the “Master clock”, since a master clock is installed there and it transmits phase reference information to other upstream synchronization nodes, in order to slave the clocks of these nodes to its own clock. Conversely, the synchronization terminal node No is designated as the “Slave clock”, since its clock is slaved to that of another node located upstream, by means of the phase reference information transmitted by the latter. Finally, any intermediate syn node Ni can be referred to as a "Boundary clock" when it has its own clock that can synchronize, this type of node acting both as a master (to other downstream nodes) and as a slave (to other upstream nodes).

[0012] The operator of the NET network may need to diagnose the synchronization network of this NET network when it suspects that a synchronization problem is causing a malfunction of this NET network.

[0013] Thus, in the case of a 5G telecommunications network, the implementation of a phase synchronization network being complex due to a multitude of equipment involved, breakdowns can be frequent, which leads to service interruptions requiring rapid diagnosis.

[0014] However, at this stage, there is no satisfactory solution for diagnosing, reliably and automatically, a synchronization network, and in particular for obtaining a real image of this synchronization network at a given time. The synchronization network is presumed to correspond to the equipment nodes crossed by the data traffic and, in case of doubt, the operator will have to connect manually, one by one, to the equipment nodes likely to be synchronization nodes, in order to check whether this is indeed the case and thus trace the synchronization network.

[0015] Certainly, the ITU-T G 8275.1 standard defines, in its appendix D, an option called "Path trace" in which additional information can be added by each synchronization node crossed in a message, addressed in the downward direction, to a synchronization node located downstream in the synchronization network. One could therefore imagine a solution based on the addition of additional information such as the identifiers of the synchronization nodes, step by step by each of the successive synchronization nodes, so that an overall image of the synchronization network is available at the level of the terminal synchronization node, and can be taken there by the network operator for the purpose of diagnosis.

[0016] However, such a solution relies on the prerequisite that each of the synchronization nodes supports such an option, which is far from being the case currently in practice and cannot be completely guaranteed in the future. And even if this option were to be deployed more widely in the future, it is sufficient for a single synchronization node not to support this option, in the synchronization chain, for there to be an interruption in the transmission of this additional information, and therefore an impossibility of obtaining a global image of the synchronization network at the level of the final synchronization node. Statement of the invention

[0017] The present invention aims to remedy the drawbacks of the implementation proposed above, by proposing a synchronization network discovery method which does not have the drawbacks of this implementation, and which is notably more reliable than this one while being automatic.

[0018] To this end, a method is proposed for discovering, within a network, a synchronization network comprising a set of synchronization nodes, said method being implemented by a management device connected to at least one of said synchronization nodes, comprising the following steps:

[0019] performing a verification by means of the clock identifier previously obtained from one of said synchronization nodes, said clock identifier being associated with a synchronization node providing synchronization information to said synchronization node from which said clock identifier is obtained; and

[0020] depending on the result of said verification, obtaining a new clock identifier from said synchronization node associated with said previously obtained clock identifier, said new clock identifier being associated with a synchronization node providing synchronization information to said synchronization node associated with said previously obtained clock identifier.

[0021] Thanks to such a method, at least partial discovery of the clocks used in the synchronization network can be carried out, simply and efficiently, by means of retrieving from a node of this synchronization network, via a standard interface, information commonly available in a synchronization network, without it being necessary to activate a specific option on all the nodes of the synchronization network to be discovered.

[0022] In one embodiment, this method further comprises, depending on the result of said verification, adding a new identifier of a synchronization node associated with said previously obtained clock identifier, to a list of identifiers of synchronization nodes intended to be made available. This allows at least partial discovery of the nodes constituting the synchronization network, based on the clocks discovered by means of information currently available from the synchronization nodes.

[0023] In another embodiment of this method, the steps of obtaining and adding are repeated as long as the result of said verification is positive. This allows the most complete discovery possible of a synchronization network, depending on the architecture and the operating state of this synchronization network.

[0024] In one embodiment of this method, the verification comprises searching, in a list of clock identifiers respectively associated with synchronization node identifiers, for a correspondence between said previously obtained clock identifier and a synchronization node identifier; and

[0025] when no match is found between said prea clock identifier lably obtained and a synchronization node identifier in said list, at least one action is triggered among the emission of an alert message and the updating of said list of clock identifiers respectively associated with synchronization node identifiers.

[0026] Thus, the process of discovering the synchronization network makes it possible to alert on the presence of an unknown clock in the network or to complete the information relating to a synchronization node not yet identified.

[0027] In another embodiment of this method, which can be combined with the previous one, the verification comprises a comparison between the previously obtained clock identifier and a clock identifier associated with a synchronization source node of said communication network; and

[0028] when a correspondence exists between the previously obtained clock identifier and a clock identifier of a synchronization source node of said communication network, said list of synchronization node identifiers is made available, preferably with an indication that said list is complete.

[0029] This clock identifier associated with a synchronization source node of said communication network may in particular be obtained from said synchronization node providing said previously obtained clock identifier, in order to allow their comparison.

[0030] The discovery process can thus stop as soon as the synchronization network is completely discovered, the operator being able to be notified on this occasion of the completeness of this discovery.

[0031] In another embodiment of this method, which can be combined with the two previous ones, the verification comprises a comparison between said previously obtained clock identifier and a clock identifier associated with said synchronization node from which said clock identifier is previously obtained; and

[0032] when a match exists between said previously obtained clock identifier and a clock identifier associated with said synchronization node from which said clock identifier is previously obtained, said list of synchronization node identifiers is made available, preferably with an indication that said list reflects a degraded synchronization path.

[0033] The discovery process can thus stop as soon as a clock of a synchronization node is synchronized with itself, which can happen with “border node” type nodes which have their own clock, the operator being able to be warned on this occasion of the degraded nature of the synchronization network thus discovered.

[0034] In a particular embodiment, said previously obtained clock identifier and said clock identifier, associated with said synchronization node at from which said clock identifier is previously obtained, are obtained in the same message from said synchronization node, received in response to sending a request to obtain said identifiers.

[0035] In a particular embodiment, said clock identifier, associated with said synchronization node from which said clock identifier is previously obtained, is a value of a parent clock identifier field compliant with the ITU-T G 8275.1 / Y.1369.1(11 / 22) standard, said parent clock identifier field being received, in said synchronization network, by each synchronization node from its parent synchronization node. In another embodiment, said previously obtained clock identifier is a value of a clock identifier field compliant with the ITU-T G 8275.1 / Y.1369.1(11 / 22) standard.

[0036] There is also provided a network management device capable of discovering, within a network, a synchronization network comprising a set of synchronization nodes, said device comprising at least one processing module configured to:

[0037] performing a verification by means of the clock identifier previously obtained from one of said synchronization nodes, said clock identifier being associated with a synchronization node providing synchronization information to said synchronization node from which said clock identifier is obtained; and

[0038] depending on the result of said verification, obtaining a new clock identifier from said synchronization node associated with said previously obtained clock identifier, said new clock identifier being associated with a synchronization node providing synchronization information to said synchronization node associated with said previously obtained clock identifier.

[0039] In a particular embodiment, this management device further comprises a storage module capable of storing a list of synchronization node identifiers with a view to making it available, said at least one processing module being further configured to, depending on the result of said verification, add to said list a new identifier of a synchronization node associated with said previously obtained clock identifier. Brief description of the figures

[0040] Other characteristics and advantages of the invention will appear more clearly on reading the following description of particular embodiments, given as simple illustrative and non-limiting examples, and the appended drawings, among which:

[0041] [Fig-1] [Fig.l], already discussed, schematically illustrates a traditional architecture network concept including traditional synchronization networks;

[0042] [Fig.2] [Fig.2] schematically illustrates a network architecture in which can be implemented a management device according to an embodiment of the present invention; and

[0043] [Fig.3] [Fig.3] represents the steps of a synchronization network discovery method according to an embodiment of the present invention. Description of the invention

[0044] Reference is now made to [Fig.2], which schematically illustrates a network architecture in which a management device according to an embodiment of the present invention can be implemented.

[0045] In this architecture, where the network NET is similar to that already discussed in relation to [Fig.l], a management device 10 implements the method according to an embodiment as described below.

[0046] This management device 10 can communicate with the network nodes of the NET network, and in particular with the synchronization nodes forming a synchronization network within the NET network (eg the nodes Ns, Ni+i, Ni and No), in order in particular to obtain information from these synchronization nodes. Such a management device can in particular belong to the ISNET information system managing the NET network, and thus have the interfaces usually available between the network nodes and this information system.

[0047] From a hardware point of view, the management device 10 may comprise a communication module 20, capable of communicating with the synchronization nodes through an interface provided for this purpose (for example by means of an SSH connection) and in particular capable of transmitting requests to these synchronization nodes and obtaining in return certain information, including in particular synchronization information held by these synchronization nodes.

[0048] In particular, this communication module 20 can receive, from each of the synchronization nodes, a clock identifier corresponding, for a given synchronization node Ni (which can also be designated by “current node”), to a clock identifier Ck_idi+i associated with another synchronization node Ni+i, which can be designated as being the “parent node” of the current node, because it provides synchronization information (SYNCi+i in [Fig.2]) to this current node.

[0049] Indeed, in the synchronization network illustrated in [Fig.2], the synchronization nodes transmit from one to another not only synchronization information (such as phase reference information), allowing a current node to synchronize with its parent node transmitting this information to it, but also a clock identifier associated with the node transmitting the synchronization information. Thus, as illustrated in [Fig.2], the node Ni+i transmits to the node N; synchronization information SYNCi+i and an identifier Ck_idi+i of a clock associated with it.

[0050] This clock identifier may in particular be an identifier of a clock card incorporated in the node transmitting the synchronization information to nodes located downstream. Such an identifier may be presented as described in the IEEE 1588-2019 standard, in particular in the form of a value of type IEEE EUI-64 (Extended Unique Identifier) ​​coded on 8 bytes.

[0051] For example, in a synchronization network conforming to the ITU-T G 8275.1 standard, this clock identifier can in particular be inserted, for processing and / or transmission, in “ClocklD” and “Parent ClocklD” fields.

[0052] Such an identifier “ClocklD” is unique in the PTP network where the clock it identifies is located, and can be constructed from one of the MAC addresses of the synchronization node (for example 0x112233445566) in the middle of which the two characteristic bytes OxFFFE are inserted (which here gives a value of “ClocklD” equal to 0xll2233FFFE445566).

[0053] Thus, the management device 10, by requesting a synchronization node Ni to obtain the information “ClocklD” will receive in return at least one identifier Ck_id; of a clock associated with the node Ni (eg of a clock card incorporated in this node Ni).

[0054] When a single clock is associated with this node Ni (eg because this node N, only has a single network card managing the synchronization), a single identifier Ck_idi is then received. But there may be cases where the node Ni is associated with several clocks, for example because it includes a first network card receiving the synchronization information from an upstream synchronization node, as well as one or more network cards sending synchronization information, via the output ports of the node N;, to nodes located downstream. In this last case, the identifiers Ck_id; (“ClocklD” in the case of the IEEE 1588 standard) of these different network cards can be received from this node N;.

[0055] Furthermore, the management device 10, by requesting a synchronization node Ni to obtain the “Parent Clock ID” information, will receive in return the identifier Ck_id i+i of a clock associated with the node Ni+i (eg of a clock card incorporated in this node Ni+i) providing synchronization information to the node N;. This latter functionality, making it possible to simply obtain from a synchronization node information concerning the clock of the node located directly upstream in the synchronization network, can then be exploited by the method according to an embodiment of the invention, as will be seen below.

[0056] The management device 10 further comprises a processing module 30, itself comprising one or more processors capable of executing the steps of the method described below, in particular by executing instructions of a computer program stored on a computer program medium. In particular, the module processing 30 may comprise a single processor executing all of the steps of the method described below, but may also comprise several separate processors (for example carried by different cards, or even located in separate physical devices communicating with each other) each executing part of these steps, depending on the implementation chosen.

[0057] The management device 10 may also comprise a storage module 40 capable of storing in memory information useful to the method described below. Thus, in one embodiment, this storage module may store a first list L1 gathering the identifiers of synchronization nodes belonging to the synchronization network to be discovered. The method described below will then seek to complete, as much as possible, this list L1 in order to discover this synchronization network.

[0058] Here, an identifier of a synchronization node can take any form allowing an operator to identify, with great certainty, a synchronization node. It can in particular be a unique identifier such as a MAC address of the synchronization node, or an IP address associated with this node.

[0059] This storage module 40 can also store a second list L2 in which, for a plurality of synchronization node identifiers, each identifier id(Ni) of a synchronization node Ni is respectively associated with at least one clock identifier Ck_id; identifying a clock incorporated in the node N; thus identified. Such a list L2 thus makes it possible to find, from the identifier of a clock, the identifier of the synchronization node incorporating this clock, and vice versa.

[0060] Finally, the management device 10 also comprises a user interface module, comprising for example a screen, in order in particular to make the list L1 available to an operator once it is available, as well as to emit alert messages as will be seen below.

[0061] Reference is now made to [Fig. 3], which illustrates the steps of a synchronization network discovery method according to an embodiment of the present invention.

[0062] This method can start with a preliminary step of obtaining (step 100), from a first synchronization node (eg Noen [Fig.2]), a clock identifier (eg Ck_idi in [Fig.2]) associated with a synchronization node (eg Ni in [Fig.2]) providing the first node No with synchronization information (eg SYNCi in [Fig.2]), in other words a clock identifier associated with the parent node of the first node No.

[0063] This first node No can be chosen arbitrarily by the operator of the NET network in which one seeks to discover the synchronization network. It is ideally a terminal synchronization node, located at the end of the synchronization chain, in order to discover the synchronization network as completely as possible, but it can also be a synchronization node concerned by a user complaint, either directly or because it manages the synchronization of equipment concerned by this complaint.

[0064] For example, in the context of the ITU-T G 8275.1 standard, this preliminary step consists of obtaining from this node No the value of the identifier “Parent Clock ID” known to this node No, which identifies a clock associated with the parent node Ni providing a phase synchronization reference to this node No.

[0065] Once this clock identifier has been obtained (which can then be designated by "previously obtained clock identifier"), the method comprises a verification step (step 200) using this previously obtained clock identifier, in order to determine whether it is directly possible and / or useful to try to obtain another clock identifier, from another synchronization node located upstream, in order to continue the discovery of the synchronization network. Such a verification may comprise a certain number of particular verifications, based on different criteria, as will be seen later.

[0066] If the result of this verification is positive, in other words if it turns out that it is directly possible and / or useful to try to obtain another clock identifier from another upstream synchronization node, the method continues with a step of obtaining (step 300), from a synchronization node associated with the previously obtained clock identifier, another clock identifier associated with another synchronization node providing synchronization information to this synchronization node associated with the previously obtained clock identifier. This other clock identifier can also be designated by “new clock identifier” in order to distinguish it from the previously obtained clock identifier.

[0067] Thus, as illustrated in [Fig.2], and applied in the context of the ITU-T G 8275.1 standard, this step consists, after having obtained a first identifier “Parent Clock ID” known to the node No, in obtaining from the node Ni a second identifier “Parent Clock ID” known to this node Nb this second identifier “Parent Clock ID” identifying a clock of a parent node N2 providing a phase synchronization reference to this node Ni (itself parent of the first No).

[0068] At this stage, several clock identifiers associated with different synchronization nodes being recovered by the management device, it becomes possible to discover, at least partially, successive clocks (and therefore indirectly synchronization nodes) in the synchronization network, and this from information simply obtained through an existing connection between the synchronization nodes and the management device 10.

[0069] The verification and obtaining steps described above (steps 200 and 300) can then be repeated, considering the new clock identifier obtained during an obtaining step 300 as being the “previously obtained clock identifier” used during a following verification step 300. Such an iteration is illustrated in [Fig.3] by the incrementation of the variable i before step 300, which then loops back to the verification step 200.

[0070] We then obtain, at each iteration of these two verification and obtaining steps (steps 200 and 300), a new clock identifier Ck_idi+i associated with a new synchronization node Ni+i, which allows an increasingly complete discovery of the synchronization network, going back into it.

[0071] In particular, in a particularly advantageous embodiment, these two steps are repeated as long as the result of the verification at each iteration is positive, i.e. as long as it is directly possible and useful to repeat these steps, in order to obtain the most complete image possible of the synchronization network.

[0072] Thus, taking the example illustrated in [Fig.2] in the context of the ITU-T G 8275.1 standard, the clock identifier Ck_idi associated with the node Ni is first obtained from the terminal node No, then the clock identifier Ck_id2 associated with the node N2 is obtained from the node Ni. As long as this is deemed possible and useful, the method continues by obtaining, from a node Ni, the clock identifier Ck_idi+i associated with its parent node Ni+i (i.e. which provides it with a phase synchronization reference), and so on until this is no longer deemed directly possible and / or useful.

[0073] From an iteration where the result of the verification is negative (either because it is no longer directly possible to repeat these steps, or because it is no longer useful to do so, as will be seen below), the list of clock identifiers can be considered as not being able to be completed further, and thus serve as a basis for the identification of the synchronization nodes, associated with these clock identifiers, which are the best possible representation (even partial) of the synchronization network.

[0074] The method may also comprise, depending on the result of the verification step, the addition (step 220) of a new identifier id(Ni+i)) of a synchronization node, associated with the previously obtained clock identifier, to a list L1 of synchronization node identifiers intended to be made available. Thus, as clock identifiers are obtained, this list L1 is enriched with the synchronization node identifiers associated with these clock identifiers, and may be made available to the operator of the NET network so that it has an image of the synchronization network in its NET network.

[0075] As regards the verification (step 200), this may firstly comprise a search step (step 210), in a list L2 of associated clock identifiers respectively to synchronization node identifiers, of a correspondence between the previously obtained clock identifier and a synchronization node identifier.

[0076] If such a correspondence exists, and therefore a synchronization node identifier has been found to be associated with the clock identifier previously obtained in the list L2, the result of the verification (step 200) is positive in that it is directly possible to continue the method using this synchronization identifier thus found (for example, when the identifier found is an IP address of a synchronization node, by sending to this node a request to obtain a clock identifier with this IP address as the destination address in this request).

[0077] The method then continues, advantageously by a step of adding (step 220) in the list L1 the synchronization node identifier thus found, as described previously, as well as by obtaining a new clock identifier (step 300) from a new synchronization node, by means of the synchronization node identifier thus found (for example by sending a request for obtaining with the IP address, identifying this new node, as the recipient address of this request), and a new verification iteration on the basis of this new clock identifier, as discussed previously.

[0078] Thus, to return to the example previously discussed from [Fig.2], when the node No provides a clock identifier Ck_idi which is associated, in the list L2, with an identifier Id(Ni) of the node Ni providing a phase synchronization reference to the node No (for example the IP address of this node Ni) the association is found during this search step 210 and the identifier Id(Ni) can be added to the list L1, so that L1={ Id(N0); Id(Ni)}.

[0079] If, on the other hand, such a correspondence does not exist, the result of the verification (step 200) is negative in that the management device 10 is not able to directly identify the parent synchronization node to contact to obtain a new clock identifier and, at this stage, cannot go further upstream in the chain of synchronization nodes.

[0080] The management device can then trigger an action in reaction to this blocking situation, which can be the transmission (step 211) of an alert message, intended for the operator of the network NET, in order to warn it that the discovery process is interrupted due to a lack of information on the synchronization nodes or the detection of an unknown clock in the synchronization network.

[0081] Alternatively or in addition to this alert, an action to be triggered may be the update (step 213) of said list L2 in order to add thereto, in association with the new clock identifier obtained, the identifier of a synchronization node in which is located the clock identified by this new clock identifier obtained. Once this L2 list is updated, the process can then continue by querying, using the synchronization node identifier which has just been added to the L2 list, this synchronization node in order to obtain a new clock identifier.

[0082] The verification (step 200) may further comprise a first comparison (step 230) between the previously obtained clock identifier and a clock identifier Ck_ids associated with a synchronization source node of said communication network.

[0083] Indeed, in an advantageous embodiment, the identifier(s) Ck_ids of the source clock(s) used in the network NET are previously stored (for example in the storage module 40), so as to be able to subsequently carry out this first comparison, each time a new clock identifier is obtained from a synchronization node.

[0084] In another advantageous embodiment, the identifier(s) Ck_ids of the source clock(s) used in the network NET is retrieved from the node Ni, providing the clock identifier Ck_idi+i previously obtained to the management device 10 (as illustrated in [Fig.2]), typically at the same time as the latter, for example within the same response message to a request for obtaining transmitted from the management device 10 to this node Ni. In particular, in the context of the ITU-T G 8275.1 standard, it may be the identifier “GMclocklD” (for “Grand Master clock ID”).

[0085] When the result of this first comparison is that a correspondence exists between the previously obtained clock identifier and a clock identifier Ck_ids of a synchronization source node of said communication network, the verification (step 200) has a negative result in the sense that it is no longer useful to seek to obtain a new clock identifier of a new upstream synchronization node, since the last clock identifier obtained identifies a source clock of the synchronization network and therefore the synchronization network has already been discovered up to its source.

[0086] In such a situation, the list L1 of synchronization node identifiers can be made available (step 240). In other words, the list L1, stored until now without necessarily being shared, is made available and consultable, for example through the interface module 50 where this list L1 can be presented either as is, in a raw form corresponding to a series of identifiers (e.g. MAC or IP address), or in a reprocessed, more user-friendly form, such as a graphical representation of the NET network highlighting the nodes identified by this list L1 within the NET network.

[0087] Preferably, this provision may be accompanied by an indication that the list L1 is complete (step 235), which can be displayed at the same time as list L1, for example in the form of a specific icon added to the aforementioned graphical representation.

[0088] On the other hand, when the result of this first comparison is that no correspondence exists between the previously obtained clock identifier and a clock identifier Ck_ids of a synchronization source node of said communication network, the verification (step 200) has a positive result in the sense that it is useful to seek to obtain a new clock identifier from a new synchronization node which cannot be a synchronization source node, by means of the previously obtained clock identifier, in order to continue to discover the synchronization network further upstream. A new step of obtaining (step 300) a new clock identifier can then be implemented, as discussed previously.

[0089] The verification (step 200) may further comprise a second comparison (step 250) between said previously obtained clock identifier Ck_idi+i and another clock identifier Ck_id;, associated with said synchronization node Ni from which said clock identifier is previously obtained.

[0090] This other clock identifier Ck_id; may in particular be the clock identifier previously obtained from a previous synchronization node (during a previous iteration of the verification and obtaining steps), i.e. from the synchronization node Nm directly downstream from the synchronization node Ni. This other clock identifier Ck_id;, previously obtained from the node Nm, being stored by the management device 10 (in particular in the list L2 making it possible to find the identifier of the associated node Ni), it can then be recovered to be compared with the new clock identifier Ck_idi+i obtained from the node Ni.

[0091] Alternatively, this other clock identifier Ck_id; can be obtained from the same synchronization node N;, and advantageously at the same time as the clock identifier Ck_idi+i associated with a parent node of the node N; is obtained from this node Ni, as illustrated in [Fig.2].

[0092] Thus, to take the example illustrated in [Fig.2] in the context of the ITU-T G 8275.1 standard, the management device 10 can send a request to a node Ni in order to obtain in return, in a response message sent by the node N;, not only the “Parent Clock ID” identifier known to this node Ni as already indicated previously, but also the “Clock ID” identifier known to this node Ni, in order to compare these two identifiers.

[0093] During this second comparison, it is determined that a correspondence exists between these two clock identifiers Ck_id; and Ck_idi+il when these two identifiers are identical. In an advantageous embodiment, even when these two iden identifiers are not identical, one can nevertheless check whether they are not both associated with the same synchronization node, for example by searching in the L2 list discussed previously. If this is the case, then a correspondence exists between these two identifiers, since they identify two clocks located in the same synchronization node (for example in the form of two separate clock cards inserted in this equipment).

[0094] When the result of this comparison is that a correspondence exists between said previously obtained clock identifier and a clock identifier associated with said synchronization node from which said clock identifier is previously obtained, the result of the verification (step 200) is negative in the sense that it is no longer useful or directly possible to seek to obtain a new clock identifier from a new upstream synchronization node, since the last clock identifier obtained identifies a clock from the same synchronization node as the one already identified previously, or even the same clock as the one already identified.

[0095] This is then symptomatic of a situation where the synchronization node Ni is synchronized with itself, as may be the case with a boundary node (“boundary clock” in English) compliant with the PTP (“Precision Time Protocol” in English), and in particular a T-BC (“Telecom Boundary Clock”) clock in “holdover” mode (i.e. which runs on its own clock because it no longer has an available synchronization reference). It is then no longer possible to go further upstream from such a node in the discovery of a synchronization network.

[0096] In such a situation, the list L1 of synchronization node identifiers may be made available (step 240), under the same conditions as described previously in relation to a positive result of the first comparison, with the difference that this provision may preferably be accompanied by an indication that the list L1 reflects a degraded or faulty synchronization path (step 255), which may be displayed at the same time as the list L1, for example in the form of a specific icon added to the aforementioned graphical representation.

[0097] In an advantageous embodiment, the verification (step 200) comprises the search, the first comparison and the second comparison (steps 210, 230, 250) as previously discussed, so that obtaining a new clock identifier is only repeated when this proves to be directly possible and useful. However, the verification (step 200) may also comprise only one, or only two, of these search, first and second comparison steps (steps 210, 230, 250), depending on whether it is desired to condition this reiteration solely on its usefulness or solely on the fact that it is directly possible.

[0098] Of course, the invention is not limited to the embodiments described and shown above, from which other modes and other embodiments may be provided. embodiments, without departing from the scope of the invention.

[0099] Thus, an example of application to the specific case of a fifth generation mobile network has been described, but the invention can be applied not only to any type of telecommunications network, of any generation, but more generally to any type of equipment network in which there is a network of synchronization nodes in which nodes transmit synchronization information to each other step by step.

[0100] Furthermore, an example of a synchronization network using a PTP ITU-T G 8275.1 profile according to the IEEE 1588 standard has been described, but the invention can be applied to any synchronization network using any synchronization protocol provided that this protocol is based on the transmission of information between neighboring nodes of this network, and in particular information such as the clock identifiers associated with these nodes as well as synchronization information such as phase, time or frequency reference information making it possible to synchronize the node receiving this information with other neighboring nodes in this network.

Claims

Claims

1. Method for discovering, within a network (NET), a synchronization network comprising a set of synchronization nodes, said method being implemented by a management device connected to at least one of said synchronization nodes, comprising the following steps: Carrying out a verification (200) by means of the previously obtained clock identifier (Ck_idi+i) from one of said synchronization nodes (Ni), said clock identifier being associated with a synchronization node (Ni+i) providing synchronization information to said synchronization node (Ni) from which said clock identifier is obtained;and Depending on the result of said verification, obtaining (300) a new clock identifier from said synchronization node (Ni+i) associated with said previously obtained clock identifier, said new clock identifier being associated with a synchronization node providing synchronization information to said synchronization node (Ni+i) associated with said previously obtained clock identifier.;

2. Method according to claim 1, further comprising, depending on the result of said verification, adding (220) a new identifier (id(N i+i)) of a synchronization node associated with said previously obtained clock identifier, to a list (Ll) of synchronization node identifiers intended to be made available.

3. Method according to claim 2, wherein the steps of obtaining (300) and adding (220) are repeated as long as the result of said verification is positive.

4. Method according to one of claims 2 or 3, wherein: the verification comprises searching (210), in a list (L2) of clock identifiers respectively associated with synchronization node identifiers, for a correspondence between said previously obtained clock identifier and a synchronization node identifier; and when no correspondence is found between said previously obtained clock identifier and a synchronization node identifier in said list, at least one action is triggered among the transmission (211) of an alert message and the updating (213) of said list of clock identifiers respectively associated with identifiers of synchronization node.

5. Method according to one of claims 2 to 4, wherein: the verification comprises a comparison (230) between the previously obtained clock identifier and a clock identifier associated with a synchronization source node (Ck_ids) of said communication network; and when a correspondence exists between the previously obtained clock identifier and a clock identifier of a synchronization source node of said communication network, said list (L1) of synchronization node identifiers is made available (240), preferably with an indication that said list is complete (235).

6. Method according to claim 5, comprising obtaining, from said synchronization node (Ni+i) providing the previously obtained clock identifier, said clock identifier associated with a synchronization source node (Ck_ids) of said communication network from said synchronization node (Ni+i), in order to allow their comparison (230).

7. Method according to one of claims 2 to 6, wherein: the verification comprises a comparison (250) between said previously obtained clock identifier and a clock identifier associated with said synchronization node (Ck_id;) from which said clock identifier is previously obtained; and when a correspondence exists between said previously obtained clock identifier and a clock identifier associated with said synchronization node from which said clock identifier is previously obtained, said list (Ll) of synchronization node identifiers is made available (240), preferably with an indication that said list reflects a degraded synchronization path (255).

8. Method according to claim 7, in which said previously obtained clock identifier and said clock identifier, associated with said synchronization node (Ck_id;) from which said clock identifier is previously obtained, are obtained in the same message coming from said synchronization node (Ni), received in response to the sending of a request to obtain said identifiers.

9. Method according to one of claims 7 or 8, in which said clock identifier, associated with said synchronization node (Ck_id(;) from which said clock identifier is previously obtained, is a value of a parent clock identifier field conforming to the ITU-T G 8275.1 / Y. 1369.1(11 / 22) standard, said parent clock identifier field being received, in said synchronization network, by each synchronization node from its parent synchronization node.

10. Method according to one of claims 1 to 9, wherein said previously obtained clock identifier is a value of a clock identifier field conforming to the ITU-T G 8275.1 / Y. 1369.1(11 / 22) standard.

11. Network management device capable of discovering, within a network (NET), a synchronization network comprising a set of synchronization nodes, said device comprising at least one processing module configured to: carry out a verification (200) by means of the clock identifier previously obtained (Ck_idi+i) from one of said synchronization nodes (Ni), said clock identifier being associated with a synchronization node (Ni+i) providing synchronization information to said synchronization node (Ni) from which said clock identifier is obtained;and depending on the result of said verification, obtaining (300) a new clock identifier from said synchronization node (Ni+i) associated with said previously obtained clock identifier, said new clock identifier being associated with a synchronization node providing synchronization information to said synchronization node (Ni+i) associated with said previously obtained clock identifier.;

12. Network management device according to claim 11, further comprising a storage module capable of storing a list (L1) of identifiers of synchronization nodes with a view to making it available, said at least one processing module being further configured to, depending on the result of said verification, add (220) to said list (L1) a new identifier (id(Ni+i)) of a synchronization node associated with said previously obtained clock identifier.

Images