Service - Conformance Units - test case
Subscription Services - Subscription Client Basic - 033, 034, 036, 037, 038, 039, 040

The Client showing the current value correctly, determined by the “Timestamp”.
There's a possibility that the server is changed their time because of system time synchronized or some reason. In this case we'd like to display notification value, so we would not like to filter them using "Timestamp".
This specification is against our product philosophy.

No, our system is able to use only 1 timestamp that is filled in serverTimeStamp.
My concern is following case;

10:31
10:32
10:29 <-changed time by system synchronized
because of spec, we have to throw out it
10:30 <-because of spec, we have to throw out it
10:31 <-because of spec, we have to throw out it
10:32