text: fig1 depicts a multi - microcomputer system having three hierarchically structured network levels e1 through e3 , of which level e1 is the highest in the hierarchy . clock modules provided in the individual computers -- indicated by a clock symbol -- are each synchronized by a clock module of the next higher level . a central master clock hu directly synchronizes the clock modules of level e1 and thus determines the time of day for the entire system . a master clock module is one that synchronizes the clock modules of the level beneath it . each synchronized clock module which itself does not synchronize any clock modules of a level beneath it is called a slave . masters m1 through m5 with their network - wide identifiers ( clocknr ) and slaves s1 through s11 are present in the illustrated example . a central evaluation unit aw is also provided . in this unit , the time stamps which are output by the clock modules are : registered , tested for time consistency , and the events which trigger them are ordered as a function of time ( event ordering ). assume that masters m3 and m5 are temporarily not synchronized with the master clock hu . this could be caused by a lack of synchronization messages or by the restarting of their computer . then the master clock modules m3 and m5 would be free - running , with the result that their times of day are no longer consistent with those of the remaining system . they thus establish separate time bases . ______________________________________ e1 e2 e3______________________________________synchronization cycle [ sec ] 60 10 1clock resolution [ msec ] 10 10 1synchronization delay [ msec ] 1 . 2 0 . 5 0 . 2______________________________________ the synchronization cycle is the time interval between the synchronization or clock messages ; the clock resolution is the externally observable time raster step with which the clock module counts time ; and the synchronization delay is the maximum asynchronism that can occur within a hierarchical level between two clock modules . the synchronization delay is essentially determined by the product of the synchronization cycle and the quartz tolerance of the clock module . with respect to the slave clock modules s1 , s3 , s4 , s9 and s10 , for the above described scenario , fig2 shows the contents of the additional information fields . the left column , denoted by tel , portrays the information fields of the synchronization messages received from these clock modules . the right column , denoted by st , portrays the information fields of the time stamps output by these clock modules . one should think of the messages as well as the output time stamps as being supplemented by corresponding fields for time of day and date . these are not shown , however , for the sake of clarity . the synchronization source field , described as clocknr , contains information about the synchronization source , i . e ., the identifier of the particular master from where the received message originated . therefore , it is always the identifier of the highest synchronized master . thus the clocknr field of slave s9 is clocknr = 1 rather than clocknr = 4 . if a master clock module is unsynchronized , or if it is free - running , then its slaved clock modules are synchronized to it but not to hu . thus their clocknr fields display the unsynchronized master &# 39 ; s clocknr , and not necessarily that of the master in the highest ( el ) level . as such the clocknr field of slave s10 is clocknr = 5 rather than clocknr = 2 . the field characterized by clocknr always contains the identifier of the highest prior synchronization source . the synchronization type field , designated as vers , has three subfields for the synchronization message and four subfields for the time stamps output . the subfield denoted by f1 is characterized by t (= true ) if the synchronizing master clock module is synchronized to the central master clock hu . it is set to the value f (= false ) if it is &# 34 ; free - running &# 34 ; with its own time base . when the subfield f1 is set to the value t , f2 signifies whether the master clock hu outputs daylight savings time ( t ) or standard time ( f ). in the case that f1 = f is entered , the vers field &# 39 ; s far right subfield characterizes the current number of the active free - running phase of the master . this is the third subfield in the case of the synchronization message , and the fourth subfield in the case of the time - of - day stamp . its contents indicate how many times the master synchronizing this slave was already forced to autonomously determine the time of day of the clock modules arranged downstream from it . this may occur because of a wanted or unwanted uncoupling from the master clock due to failure , for example , of the synchronization messages or other malfunctions . in this case , it broadcasts the synchronization messages to its subordinate hierarchical levels and enters its own identifier in the clocknr field . in the scenario described , the third subfield of the vers field of the slave clock modules s4 and s10 show that the master clock modules m3 or m5 ( which synchronize them ) have shifted into a free - running phase . therefore , the number contained in the fourth subfield of the vers field can be interpreted as the current number of a newly established time base , which relates to the particular higher - ranking synchronizing master . the subfield denoted by f0 is an extension of the vers field for the time stamp . each clock module sets this subfield to the value t ( true ), when it is synchronized to a higher - ranking master clock module . of particular importance is the synchronization delay field denoted by slag , which indicates the synchronization delay . each master clock module adds the synchronization delay that is relevant for its hierarchical level to the synchronization delay broadcasted to it in the synchronization message . thus , the values of the synchronization delay in the individual hierarchical levels accumulate in this field . thus , the slag field of the message received from the slave clock module s1 reveals the value of 1 . 2 msec , while the slag field of the message received from the slave clock module s9 shows the value of 1 . 7 msec , in accordance with the sum of the synchronization delay ( 1 . 2 msec ) existing in the level e1 and the synchronization delay ( 0 . 5 msec ) inherent in level e2 . the value of the slag field in the time stamp is calculated by each clock module from the sum of the slag field in the message that it has received and of the value of the synchronization delay that is inherent for its hierarchical level . this becomes clear from a comparison of the slag fields from the received message and from the time stamps output for the individual slaves . in the field denoted by scyc , the messages intended for the clock modules show the time interval in which the synchronization messages are sent ( synchronization cycle ). this value is important for the clock module &# 39 ; s calculation of the synchronization delay . it is also used to check ( in the clock module ) the synchronization and regularity of the received messages . using this , it is possible to recognize when a master clock module has failed . finally , in the field denoted by gran , the time - of - day resolution is entered . the sum of the value input in this field and the accumulated synchronization delay input ( in the slag field ) determine the event resolution of one clock module . in this context , event resolution is understood to be the minimum interval that two time stamps must be separated for the events characterized by them to be brought into a clear time sequence , in the sense of which event occurred first in time . characterized in this manner , the event resolution is also the maximum differential error which can occur when time intervals are calculated between two time stamps . using a flow chart , fig3 shows how the additional information of a first and second time stamp , st1 and st2 , from different clock modules is used for a consistency check and for a subsequent determination of the event resolution in this synchronization scheme . first , it is checked whether the subfields f0 of the two time stamps are set to the value t ( 301 ). if they are not , the two time stamps are rejected as being inconsistent , and the error message inc is output ( 302 ). this is because no statement can be made on the basis of different time bases about which time stamp characterizes the earlier or the later event . then , it is checked if the subfields f1 have the value t in both time stamps ( 303 ). if so , it is checked to see if the subfields f2 of the two time stamps st1 and st2 have the same value ( daylight saving time or standard time ) ( 304 ). if so , the consistency test is successful . if not , the results are rejected as inconsistent ( 305 ). if both subfields f1 are not set to the value t , for example , when both clock modules are synchronized to the same free - running master , it is then checked whether the fields clocknr and vers of the two time stamps conform ( 306 ). if not , the two time stamps are again rejected as being inconsistent ( 307 ). on the other hand , if they do conform , the event resolution ea of the two time - consistent time stamps is determined ( 308 ). this is obtained , in each case , from the larger of the sums of the values in the gran and slag fields for the two time stamps . applying this flow chart to the embodiment of fig2 reveals , that using the method according to the invention , it is possible is conclusively determine time - consistent time stamps and event resolution . a continual synchronization of local clock modules to a central master clock is achieved over several hierarchically structured network levels .